>Here is the problem we have observed.
>An ODBC connection to a VFP DBC makes a change to that DBC
>Immediately after that, another ODBC connection to that same database is
>unable to see those changes.
>
>This is happening between different systems on the Web using VFP backends
>with the Microsoft VFP ODBC Driver version 6.x
>
>I know there is an article in the MSDN somewhat describing this problem.
>However, establishing a connection, killing that connection, and then re-
>establishing the connection, does not help.

How about if you close the connection that made the change? Does that work any better?