>We are trying to use views for all our tables because we want to have all our apps more prepared for a possible migratio to a client/server environment. Unfortunately we encountered that with view you loose some possibilities you have with working direct on the VFP tables.

*********

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.

I would like to use views over a network, but find it's too risky. I cannot crack the problem of damaged or ill-behaved views getting stuck in the database. I prefer the idea of querying data to a cursor (including a key field), USEing the cursor AGAIN to make it read-write, doing edits, then writing back to the database (with the key field). This is an upsizable strategy as remote querying would simply substitute for local querying.

It may sound ludricrous to reject views altogether, but consider: views reside in the DBC, which I have only intermittent access to for testing, whereas the code to run queries is all handled in my app, which I can send to the client for replacement as often as I like.

Who else thinks like this?
John Burton