This method works pretty good. Thank you all for your suggestions. I really wish the view designer worked however because it's much faster than
coding it.

>Joe,
>
>i recently faced the same problem. Instead of setting the views up at runtime (meaning anywhere in the form) i decided to write a small app CreateViews that creates the views i need in any complexity and store them to the DBC. My experience is that the DBC can hold any view, it seems to be the view designer that is simple minded.
>
>The CreateViews looks like
>
>Open Database Data\MyDBC
>Create SQL View MyView Remote ;
> Connection MyConnection Shared ;
> As ;
> Select * from AnyTable
>SetViewProperties("MyView")
>Create SQL View MyView2 Remote ;
> Connection MyConnection Shared ;
> As ;
> Select * from AnyOtherTable
>SetViewProperties("MyView2")
>...
>
>This is for remote views, the same should work with local views.
>SetViewProperties is an UDF that sets all the neccessary properties for each view. I don't have access to mu computer this moment, but it was something like:
>
>Procedure SetViewProperties(cViewName)
>Use &cViewName NoData
>DBSetProperty(cViewName, "Updatable", .T.)
>...
>
>Take a look at DBSetProperty for all properties needed (about 20) or email me again tommorrow to receive the complete sourcecode. Sorry for the delay, i'm currently flying...
>
>Joerg Karpa