>In the memo field where I have Message(2) info, a SQL command is there that I could not identofy because it had a where clause like: where 1=0. It finally dawns on me [make mental note here] that this is how VFP opens a view when the NoData option is used.

I reported this a few months back. I found it fascinating that a crack in VFP allowed us to see the SQL commands that VFP was using behind the scenes to let views operate. I have found other tidbits here as well: exactly how VFP uses the view settings you enter in the view designer to construct UPDATE DELETE and INSERT statements, the names of temp files used, etc.

After finding this, I immediately checked with a back-end database, and found that remote views are handled differently.

I tried for nearly a day and a half to be able to reproduce this anomoly dependably, so I could add the functionality to eView to let you see how your update statements are being constructed. No Dice. It only happens in a compiled exe, and even then, not dependably. I have never been able to figure out the exact set of circumstances that makes VFP substitute the last piece of internal SQL for the contents of MESSAGE(2).