Hi Chris.

Never vouched for the accuracy of Fox's error messages. <g>

LOL!!! Sad but true.

I get that; just looking at repeatability of the error to help chase it down. If only one PK change causes the break, I start thinking data; if all of them do, I start looking at code. I agree with Craig's advice that something else called during the process is the next place to look. Any UDFs in the view definition or indexes?

AFAIK, the problem only happens with this one form and this one table.

Parent view? Does this mean the broken one is a view of a view? Is the parent view the broken one?
Is it broken only in the program or will the view not open manually in Fox either?

The broken view is a subset of fields from the same table that the Parent view is based on. The parent view updates the base tables. The view that is a subset of the fields in this table is the one that the framework complains does not have the column. It is only broken when running the application, It is fine when opening the view from VFP.

Ummm.. never, actually. Saw your name on this and was intrigued enough to offer my measly 2c.
And some of these ideas are SWAGs. Even if they don't work they may spark some other idea, or at least eliminate the impossible as that Holmes guy said.

Your 2c is not measly. But I am curious, why were you intrigued?

Maybe there's subtle data corruption in the DBC? Delete and recreate the view. Validate the DBC. What forces Fox to reread the view definition from the DBC if the view is already in use? (I don't know that much under the hood stuff.) Some people have separate DBCs for views, is /that/ DBC broken?

My gut feel on this is that there is a problem somewhere in VPM's metadata, but I have browsed the metadata tables for the views involved, I can't find anything suspect.
I am almost ready to give up on this one because the only 2 people who ever see this application working against native data are another developer and me. All the production stuff is against SQL Server. But he asked me to resolve the issue (originally the cascading RI was broken). I fixed that problem, but after I did, it led to a whole bunch of new problems :(

Thanks for trying to help.