I have 2 Recordsets on 2 different applications communicating with the same
database

-=The first Recordset is opened with=-
m_pGlobal_RS->Open(adCmd, m_pConnection.GetInterfacePtr(), adOpenKeyset,
adLockPessimistic, adCmdText);

-=The second Recordset is opened with=-
local_RS->Open(adCmd, m_pConnection.GetInterfacePtr(), adOpenKeyset,
adLockReadOnly, adCmdText);

* adCmd is a simple SELECT statement that is the SAME for both recordsets.

The code order is roughly this

Open m_pGlobal_RS
...
...
Change fields on m_pGlobal_RS
...
...
MoveNext on all rows of m_pGlobal_RS until EOF then MoveFirst  // since
pessimistic every row op sends update
..
..
I then fire an event to another application which opens local_RS.

It is random whether the data opened by the second RS is the pre-update data
or the post-update data. How can this be? I opened the connection
with the default  synchronous option, isn't this asynchronous behavior?

Thanks for the help,
-=Adog

Ok, found my answer...ADO connections maintain a cache so all connections
not involved with the update must be flushed via the JRO.JetEngine object.

Ahaaaaaaa.....

That's very interesting. So if you've got, say, 3 connections open to the same
database, and you know damn well that only one of them is going to have
anything in it's cache, because it's the only one that's been used in anger so
far.... then that's the one connection that DOESN'T need refreshing?????

I've got a model of cache purging in my mind which is clearly from a different
era :-)

Roger Morton