>>My system must operate in a 'hostile environment' - poorly trained users, remote area (max 1200 baud dial-up for support), and I have infrequent access to the database.
***************
>
>If you don't have _any_ access to your dbc, you can develop all your views in a different database container, and when you get access to the main one, move the entire definition from one dbc to the other.

*************

Yes, I guess this is a good strategy. I had experimented with creating views programmatically, but this has two pitfalls: (1) the code is verbose after you've set all the attributes, (2) if you are thinking of doing a DROP VIEW before setting up the new view (to clear out an obsolete definition) someone else might be using it.

(Incidentally, vfp5 help says 'DELETE VIEW requires exclusive use of the database', which would seem to be a documentation error.)

I notice you haven't mentioned SQL views, which I have not experimented with yet.

John Burton