Hi patrick,

I never was able to determine the exact cause of the problem. In my case it 'seemed'to have something to do with doing a TABLEUPDATE() on a row buffered table twice within one transaction. I eliminated the second TABLEUPDATE() and the problem seemed to have disappeared.

I would not be surprised if it has something to do with RI code attached to the table. Are you using triggers (for RI or other purpose)? If so, are you using TAXRI or the default VFP RI builder?

Thanks,

Walter,





>Did you ever find a solution to this problem? I am having the same problem.
>
>>Hi dragan,
>>
>>>>This error is raised during the TABLEUPDATE(0, .T., cAlias) and retrieved with AERROR(). Error 1099 is undocumented and don't have a clue where to search for the solution to this problem?
>>>>
>>>>Any clues ?
>>>
>>>'Procedure cancelled' is what you get when a procedure called from inside a report, SQL statement or a stored procedure, well, cancels.
>>>
>>>My bet is that one of the triggers errored out and cancelled. That's where I'd look.
>>
>>I guess it must be something like that, since that is the only UDF code that fires on a tableupdate. Strange enough it succeeds most of the time and it's fairly difficult to reproduce the problem, but when redoing a TABLEUPDATE() after a failed transaction might cause this error. I suspect it has something to do with 2 tableupdates on the same table during a transaction but I was not able to get a clear case. Nontheless I suspect a bug in VFP 8 since the triggers called are just RI triggers and AFAIK do not contain any bugs that could cause this error.
>>I'll try to prove if it indeed are the triggers by just disabling them...
>>
>>Thanks,
>>
>>
>>Walter,