🚀 go-pugleaf

"Yogi Yang" <yogiyang007@gmail.com> wrote in message 
news:488e98b2@newsgroups.borland.com...

> Thanks for the info but this sounds absurd.

A thread has to be assigned to a COM apartment (whether that be a 
single-threaded apartment or a multi-threaded apartment) before it can 
access COM objects.  The apartment dicates how the thread can access the COM 
objects (directly or via proxies).  The OS can't detemine ahead of time how 
you want to manage your threads.  So you have to explitically 
initialize/uninitialize your threads in your code instead.  Why is that 
absurd?

> I have imported an ActiveX in the Delphi IDE.
>
> Now if I start a new blank project and place this ActiveX
> on its form and run it (by pressing F9) it runs and the ActiveX
> behaves as documented.

Because you are using it in the main thread, and the main thread has already 
been initialized for you at startup.

> But when I use this ActiveX in an existing project I keep
> getting this message.

Because your existing project is not doing the same things to initialize the 
main thread at startup.

> Can you give me code snipper as to how to call CoInitialize and 
> CoUnInitialize?

Did you look at the documentation for them yet?  They are just function 
calls, and not very difficult ones at that, ie:

    unit Unit1;

    interface
    ...

    implementation
    ...
    initialization
        CoInitialize(nil);
    finalization
        CoUninitialize();


Gambit