🚀 go-pugleaf

>>CheckSafecallResult(HRESULT hr)

It is a fix for BCB6.

>>CoInitiliaze()/CoUninitialize()

It is COM initialization. These function should be called in every thread.
COM unit calls CoInitialize() (or CoInitializeEx()) function in InitProc. In
GUI application InitProc is called in Application.Run. In console
application you may call

if InitProc <> nil then TProcedure(InitProc);

as first procedure.

Using ComObj has some advantages - it can call CoInitialize() or
CoInitializeEx() with needed parameters (see CoInitFlags in ComObj).

In DLL CoInitialize()/CoUninitialze() may need to be called too. But it is
better to call them from main application - Microsoft does not recommend
call them from DllMain (initialization/finalization sections in Delphi).
Calling these funcions from main application lets main application to
initialize COM with needed parameters.

//------------------------------------------
Regards,
Vassiliev V. V.
http://www.managed-vcl.com - using .Net objects in Delphi + ADO.Net
http://www.oledbdirect.com - The fastest way to access MS SQL Server,
MS Jet (Access) and Interbase (through OLEDB)


"Simon Elliott" <simon@nospam.demon.co.uk> �������/�������� � ��������
���������: news:zPKJWAAuwb$$IwSU@courtlands.demon.co.uk...
> Viatcheslav V. Vassiliev <support@oledbdirect.com> writes
> >You may also need to add
> >
> >#include <comobj.hpp>
> >
> >namespace System
> >{
> > void __fastcall CheckSafecallResult(HRESULT hr)
> > {
> >  OleCheck(hr);
> > }
> >}
>
> What does the above do?
>
> >CoInitialize()/CoUninitialize() - do not call them, just include ComObj
> >unit. They are needed only in dlls.
>
> I've found that when running ADO in a separate thread, or in a console
> mode program, an exception is thrown if CoInitialize is not called.
> -- 
> Simon Elliott
> http://www.ctsn.co.uk/
>
>
>
>
>
>