>Cetin,
>thanks for your time, as I read it, your solution/method, is this , create the "basic" view using the VFP designer ( i.e. don't include more than two tables in it? ), cut and paste the code ( from the SQL window ), modify the code, and then run it to create the view in your dbc ( how can you run GenDBC.prg on the dbc if the view designer won't let you save the view definition? ), this is a real shortcoming of the VFP IDE in my book, are they secretly trying to force us into using Access / SQL Server?
>
>once again, thanks a lot for your help
>
>Pete

Pete,
Close.
-Not cut&paste SQL code. Instead I cut&paste gendbc generated code (with additional dbsetprop(), cursorsetprop() code).

I can run gendbc because I do it whenever I have an intact working DBC and keep copy of generated .prg-.krt for later reference.
Also if a view definition is correct (designer might not save or open) gendbc still runs successfully. If that still doesn't help I can hack the DBC to a point.
Cetin