Hi Rene,

I've had the same problem lately and tried to search for a solution on UT (which is why I'm looking at this thread). If you haven't solved it here is my suggesion:

After your *create sql view* code block, make sure you have the statements that set up the "UpdateName" properties on every primary/foreign key field of the view, reason being if a field exists in mutiple tables/views VFP needs to know exactly which base table to update that field. For example I solved my problem by having this statement:

DBSetProp(ThisView+".mainKey","Field","UpdateName","pdm!measpict.mainKey")

in my crete sql view code block because the "mainKey" field is common in many of my tables.

Honestly I'm not exactly sure if this idea makes sense (the error message itself doesn't anyway). Alternatively (without adding that statement to your code and after the view has been created) you can try opening the view in the VFP view designer then save it back (not even necessary to change any of the settings), which should force VFP to recreate the view and solve the issue (strangely enough).

Cheers, Abe