🚀 go-pugleaf

I like to force the calling of CoInitialize & CoUninitialize by calling them
in the constructor & destructor methods respectively of a global variable...
Declare this variable when you first start the app.... The constructor is
called automatically when the app starts & the destructor is called when the
app goes out of scope or ends.....

For instance I borrowed this from a VC++ sample provided by Microsoft....

struct InitOle {
  InitOle()  { ::CoInitialize(NULL); }
  ~InitOle() { ::CoUninitialize();   }
} _init_InitOle_;


Lance Zhang wrote in message <3aca95fa_2@dnews>...
>Hi! All,
>
>
>Context:
>I build a sample DLL following a article named "Using A Data Module In A
>DLL" By Mr. Mark CashMan published on http://www.temporaldoorway.com about
>how to put a datamodule in a dll--specifically the way to initialize a
>datamodule in a DLL.
>
>When I use a combination of TDatabase and TQuery it works just fine.
>But when I substitute them with TADOConnection and TADOQuery, an
>EOleSysError stating "CoInitiliaze not yet called" is raised upon the
>constructor of TDataModule1.
>
>Is it a ADO bug or just I neglect some steps?
>
>Pleas help!
>
>Lance Zhang
>
>