So you're saying changing the
llResult=TABLEUPDATE(2,.T.,"DetailView",Errors) to
llResult=TABLEUPDATE(1,.T.,"DetailView",Errors) will trigger the error routine?

Sounds logical and I'll try it immediately.



>I dont think tableupdate will fire any errors ..
>
>because according to the help file
>
>TABLEUPDATE([nRows [, lForce]] [, cTableAlias | nWorkArea]
>[, cErrorArray])
>
>If nRows is 2, changes made to the table or cursor are committed in the same manner as when nRows is 1. However, an error doesn't occur when a change cannot be committed, and Visual FoxPro continues to process any remaining records in the table or cursor. If cErrorArray is included, an array containing error information is created when an error occurs.
>
>I hope u get the idea.
>
>
>>As I said in my previous message, I do have an error class that does just that- and it does not fire.
>>
>>>After a tableupdate()
>>>do this
>>>in the command window .
>>>
>>>?aerror(arrErr)
>>>disp memo like arrErr
>>>
>>>it will give u the errors that occured
>>>
>>>have a look at them.
>>>
>>>if u have icq / ms messenger or yahoo messenger u can chat with me
>>>
>>>give me any of ur ids ...

Peter Pirker


Whosoever shall not fall by the sword or by famine, shall fall by pestilence, so why bother shaving?

(Woody Allen)