Hi Grigore,

Having put up with the idiosynchrosies of the View Designer for long enough, I started designing my views in code and saving them in a prog called RemoteViews.Prg. This should solve your problem. This also neatly sidesteps the problems you will undoubtedly encounter if the complexity of your joins exceeds the ability of the View Designer parser to understand them. I have come across problems creating Remote Views thru the View Designer against a PostgreSQL backend. I'm not saying that the View Designer was at fault in this instance but programmatically created views solved the problem. If all your views are in a single prog you'll easily be able to find which views reference which table.

Hope this helps.

Liam



>Hello, everyone
>
>First one: does anyone know why View Designer in VFP 7 says "base tables have been changed" when I design a brand new view and I am trying to save it? if I close that message box and save the view again, it works. How this can be avoided?
>
>Second one, about remote views, too: is there a way to find fast which remote views reference a specific SQL Server table? If I modify a table in sql server, I need to open the views and change/add the fields. When one have 600 remote views in a local database, this taks isn't easy at all...
>
>Thank you.