>>>
>>>What does aError() return. Also see if thread #949319 is at any help.
>>
>>Hello Nadya,
>>
>>Thanks for your reply. I'm using VFP 6.0. aError() returned nothing. Zilch. The error that was returned with the tableupdate was -1, but no error message whatsoever.
>
>Dodi,
>
>This is the code from our base form class to handle Tableupdate (part of it). Does not look helpful, but may be will give you some ideas:
>

>IF !TABLEUPDATE(2,.F.,ALIAS(),latuerror)
>  		thisform.aerrormsg()
>  		IF thisform.ErrorNum=1583 and thisform.UsesIV  && NSL 06/28/01 Special processing for interactive table validation errors.
>  			thisform.TableValErr=.T.
>  			RETURN .F.
>  		ELSE
>  			thisform.TableValErr=.F.
>  		ENDIF
>
>  		*--- DNG 2/14/2001: Added check for -1 (Non simple commit error).
>  		IF latuerror[1]=-1		&& Non simple commit error.
>  			RETURN .F.
>  		ENDIF
>  		*--- Walk through array of failed records and resolve field collisions
>  		FOR i=1 TO ALEN(latuerror,1)
>  			GO (latuerror[i])
>      		Thisform.updatefaillog()	&& Check collisions and
>      		* -- 						Log records which failed to UPDATE due to conflict.
>  		ENDFOR
>  		RELEASE latuerror

Thanks for sharing this with me. It's greatly appreciated, however, I noticed in your code if latuerror[1] = -1, to return .F. (which would be my case)... also the whole error array returns .F. so there's no error at all whatsoever. This is one obstacle problem that is really baffling the wits out of me...