Hi Steve, You would normally expect CoInitialize to be called automatically as part of Applicaiton.Initialize. If you create an automation obejct then this certainly happens - have a look at the source for this. It is ok to call CoInit manually, but you should also (probably) call CoUnInitalize when you are done. If you are using COM objects from freds then you need to do this manually also. Just to confuse the subject, you can also use OLEInitialize and OLEUninitialize. In fact you are 'sposed to use these if you are using OLE objects rather than COM objects, but don't ask me to explain. >From: "Steven Wild" <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: Multiple recipients of list delphi <[EMAIL PROTECTED]> >Subject: [DUG]: Colnitialize >Date: Sun, 1 Aug 1999 12:20:06 +1200 > >I have imported an activeX component and created a simple test >application to see that it works. It does. > >However, when I then take that same component and add it to an >existing application I get the following error. > "Exception EOleSysError .............. > Colnitialize has not been called." > >I can not find any reference to "Colnitialize", nor do I understand >why it works in one context but not the other. > >Any help would really be appreciated. > >Steven >Steven Wild >Director >Wild Software Ltd >P O Box 33-216 >Christchurch, NZ >Ph & Fax 64 3 377-0495 > _______________________ > > Chreos Business Systems > _______________________ >--------------------------------------------------------------------------- > New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED] > Website: http://www.delphi.org.nz ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com --------------------------------------------------------------------------- New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED] Website: http://www.delphi.org.nz
