snip...

>John,
>By pure coincidence I was reading the " Visual FoxPro SQL Server Handbook" by RED this morning and there was an explanation of 1585 that goes like this: quote
>One common error with optimistic data buffering is that another user will have changed the same record from another workstation. The TABLEUPDATE() will fail and will return error 1585 into the error array.. endquote
>Then you deal with the failed tableupdate().
>I have not come across this problem and your circumstaances look to be different. You may try the FORCE paramater with tableupdate() before closing the database. Has you stored procedure left any uncommitted changes ?

We are using TABLEUPDATE(1,.T.,'tablealias') but we encountered just the same error before. But until this time, the error is not yet appearing since we PACKED the DBC.


>HTH
>
>>I am getting Error 1538 'A stored procedure is executing' when issuing a CLOSE DATABASES ALL command. I have two stored procedures, for indexes on one table in a database only. Nothing is being executed to my knowledge when I issue CLOSE DATABASES ALL.
>>
>>I can't force to let me CLOSE ALL from the command window, let alone trap it programmatically and proceed (have to quit FoxPro).
>>
>>The MS Knowledge Base is mute, but there is a hint that if another database is current, the one with the procedures can cause problems.
>>
>>Can anyone help?
>>
>>John Burton