Hi
I'm using ADO.Net and Access 2002.
I have two processes written in vc++ .net, lets call them for,
example A and B.
A opens a connection, do something and closes the connection.
Then A calls process B and waits it to finish.
B opens a connection, update the data, closes the connection and exits.
A opens a connection and reads the data that existed before
the updates made by process B.
Why?
Is the connection pooling to blame? I tried using a connection string
parameter "OLE DB Services = 0" to turn off connection pooling but
the problem still exists.
What more info do you need?
I'm using ADO.Net and Access 2002.
I have two processes written in vc++ .net, lets call them for,
example A and B.
A opens a connection, do something and closes the connection.
Then A calls process B and waits it to finish.
B opens a connection, update the data, closes the connection and exits.
A opens a connection and reads the data that existed before
the updates made by process B.
Why?
Is the connection pooling to blame? I tried using a connection string
parameter "OLE DB Services = 0" to turn off connection pooling but
the problem still exists.
What more info do you need?