Is your connection set up for asynchronous execution? I have seen "connection busy" errors with this setting. You might try to disable asynchronous execution to see if it helps. I use a shared connection, synchronous execution, table buffering and explicit tableupdate after each insert or replace instead of relying on the implicit tableupdate of row buffering and do not see connection busy with hundreds of updates per minute using SQL 2000. I have seen slow updates with ACCESS data where tableupdate returned .t. but immediate requery would not retrieve the records supposedly just updated, but introducing a 5 second wait state would allow Access to catch up. "Fetch data in background" setting for VFP data source connections has also caused some problems with invalid results for some queries.

HTH