🚀 go-pugleaf

"Yogi Yang" <yogiyang007@gmail.com> a �crit dans le message de news: 
488e98b2@newsgroups.borland.com...
> Marc Rohloff [TeamB] wrote:

>> Initialization of the COM (ActiveX/DCOM) framework. You need to make
>> sure that CoInitialize* is called on every thread that uses COM.
> 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.
>
> But when I use this ActiveX in an existing project I keep getting this 
> message.
>
> What must be the problem?
>
> Can you give me code snipper as to how to call CoInitialize and 
> CoUnInitialize?

In the new blank project, the main process is using (creating, calling, etc) 
the COM object. So it works.
In the existing project, a thread is doing it.

So in the thread's Execute procedure, you must enclose your existing code 
within a CoInitializeEx call at the beginning, and then a CoUninitialize at 
the end, with a "try-finally" as shown:

TYogisThread.Execute()
begin
 CoInitializeEx(nil,COINIT_APARTMENTTHREADED);
 try
   //the rest of your existing code
   finally
    CoUninitialize;
   end;

For more about the COINIT_APARTMENTTHREADED parameter, and other choices, 
look up the CoInitialize function in the Win32 Help.

Z