Thanks everyone for his/her suggestions to my problem.

The Good News: I'm relieved to inform all of you that the problem have been solved.
The Bad News: I don't know exactly what was wrong in the first place.

I tinkered with it (e.g. commenting out pieces of code here and there) this morning and all of a sudden it started working. What's more weird is, I'm now trying to duplicate the problem again so that I could find out exactly what went wrong and I can't! Originally, I though I trace the problem to multiple TABLEUPDATE() calls with latter calls that involved no data changes (although the error was generated from first TABLEUPDATE call) but I could do this now w/o any errors. I've copied over a same form from backup that wasn't working and now it works perfectly. This tells me the problem was view related and not codes within the form. Maybe I should just be happy it now works and move on but I just got to find out why.


>John:
>
>Have you tried to use the GENDBC or similar utility to get the code VFP is using to create the view and set the field update properties? If you can get a look at this code you may be able to find the problem easier. If nothing else, you could use the code, tweak it if necessary, delete then recreate the view programmatically including all the updating properties.