Heh, what a coincidence. When searching for a different problem I ran across this one in the MS KB. The knowledge base article is: Q217082 - Connection Busy Message With Remote Views of SQL Server Tables. http://support.microsoft.com/support/kb/articles/Q217/0/82.ASP. Basically, the solution is to set the FetchSize of the view to -1, e.g. =DBSETPROP('MyView','View','FetchSize',-1).

Barbara, this should allow you get rid of the loop trapping for the error and repeating the command.




>Steve,
>I just solved that one! VFP sends off the Remote View command and then goes on to the next command without waiting for the command (use, TableUpdate() etc.) to complete. That may not be the actual fact, but it sure seems to be the 'appearance'. If another view tries to use the same connection, it's error 1541. I just trap for it and repeat the command. How many times (and what the wait between tries is) depends on the circumstances. Works fine. I'm planning to write it into my error handler so I can have a variable that will control the number of retries before I have to exit.
>
>HTH
>Barbara
>
>>I'm working on converting data from a VFP Database to an Informix Database. I'm getting FOX ERROR 1541 "Connection is busy" during my =tableupdate(.t.,.t.) command on my remote views. This results in the transaction being rolled back. Does any one know why this happening?
>>
>>Should my views be sharing a connection or should I have a connection for each view? Should the connection be asynchronous?
>>
>>Thanks in advance.
>>
>>Steven Summers