I have an application blowing up with an error message saying 'Connection Connect1 is busy'. (Connect1 is the connection name specified in the DBC). It isn't easy to tell exactly where the error occurs; probably in SQL Server. This is MS SQL Server 2000. When the program bombs, VFP shows the current instruction as an ENDSCAN. Not likely, I don't think, even though that always is the line displayed. I have run SQL Profiler and see gobs of I/O being performed right before the crash. These appear to be the commands updating a SQL Server table which is set up as a remote view in VFP. The updates appear to have been optimized or modified by SQL Server. The SQL command updates the same fields specified in the VFP view designer but refers to them by names like @P1, @P2, and so on.

The current release of the application was compiled in VFP 6. I have run it in VFP 8 with the same result.

As you may have guessed by this point, I know SQL reasonably well but am not an expert on SQL Server. It would be great if we had a DBA, but we don't.

I tried setting breakpoints on SQLGETPROP( 1, 'CONNECTSTRING') and SQLGETPROP( 2, 'CONNECTSTRING') -- the two connection handles used by the app -- but don't see anything which appears amiss there.

Has anyone seen this error and can you give me any advice what to look for? I have been working on this since last week and the client is getting antsy. Thanks a million to anyone who can give me some advice.

Mike