🚀 go-pugleaf

CoInitialize( 0 ) must be called by each thread to initialize the COM layer.
When you drop one of the ADO objects on a form, this is done automatically
for the man thread.

My opinion would be to go with one connection per thread, especially if
you're using transactions.

- Arnie

"Don Wilcox" <dwilcox@dfsaz.com> wrote in message news:3cfb8db2$1_1@dnews...
>
> I have a multi-threaded program that is going to need to update a SQL
Server DB. How do I setup the connection objects for each thread? I tried
creating a single connection object on the UI form and sharing it among the
various threads. This doesn't give me any initial problems, but I worry
about threading issues.
>
> I tried dropping a separate TADOConnection object on the UI form for each
thread, but if the thread attempts to set Connected to true, the program
raises the exception EOleException 'CoInitialize has not been called'.
>
> In short, what is the correct mechanism for using TADOConnections in
multi-threaded apps?
>
> Thanks,
>
> Don