>>Does anyone know if there's are bugs with tableupdate in VFP5?
>>Problem is that sometimes it seems to move the record pointer of the table being updated, in this case a new record. It looks like it might move the pointer after it saves the data to the record.
>
>Hi Harry,
>
>Yes there is "bug" in the tableupdate in VFP5 (and 6 by the way). I spent days finding one out that happened only on NT4 (services pack levels 1-2-3 tested) - not WIN95/98 when some specific update would take place on a remote view (making a date null).
>
>This bug just crashed the VFP or exe session. We circumvented the pb by chance in moving our code from:
>
>IF TABLEUPDATE(param1,param2,param3)
>
>ENDIF
>
>to
>
>SELECT (param3)
>lSuccess = TABLEUPDATE(param1,param2)
>IF lSuccess
>
>ENDIF
>
>Do not ask me why it did do it.. i dunno. Luck I suppose and
>13 years of Fox experience...
>
>What i am pretty sure is the TABLEUPDATE command has BUGS!
>
>Good luck
>
>François

François,
I feel relieved knowing there are bugs and I'm not crazy. BTW, I have worked around this problem by saving the record # before the offending code, and then explicitly GO back to it after the TABLEUPDATE. Seems to work OK now...I'll see what happens after I release this version...
- Harry