🚀 go-pugleaf

No. If Connection will go out of scope, no close/release are called and no
methods will be available (may be instead of Release). Release is called
automatically by Variant destructor.

//------------------------------------------
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:l7kM7DARmf+$IwaV@courtlands.demon.co.uk...
> (Reposted in case anyone missed it due to the Christmas/New Year break)
>
> I'm creating an MS Access database with:
>
> Variant Catalog;
> Variant Connection;
> CoInitializeEx(NULL, COINIT_MULTITHREADED);
> Catalog=Variant::CreateObject("ADOX.Catalog");
> Catalog.Exec(Function("Create") << strConnectionString);
> Connection = Catalog.Exec(PropertyGet("ActiveConnection"));
> ...
> Connection.Exec(Function("Close"));
> CoUninitialize();
>
> Do I need to do anything special to close/release Catalog and
> Connection?
>
> What happens if Catalog and Connection go out of scope after the
> CoUninitialize() call? Will this mean that an implicit close/release
> happens after CoUninitialize(), and if so, will this cause problems?
> -- 
> Simon Elliott
> http://www.ctsn.co.uk/
>
>
>
>
>
>