>Thanks for the quick response. I guess I can do that, but I'm not sure what VFP is doing differently when you let it open the views automatically. I read somewhere that the view record in the DBC is momentarily locked when someone opens a view (or I think that's what they said - it's been awhile). I'll have to try to Google that. I could add some code that traps any error and retries at least for a few seconds until the view is opened, but it would seem VFP would do this. Especially if they know that the view's record in the DBC is indeed locked when someone is opening a view. But maybe they didn't put any retry code in there - who knows. Thanks again for your reply.

The thing which helps in this case is to have views in a separate database, and have each user have a private version of such a dbc. It's easy to tweak the code that GenDbc creates to make this done automatically, i.e. to re-create such a database on user's local disk whenever the underlying tables change.

I was doing this since VFP 5.0 and never had any problems, except the delay when this database is created, because Create Sql View command actually runs the SQL; it has no NoDataOnLoad clause that I know of. It helps, though, if your views are parametrized and you set the parameter to an impossible value before creating the view, so you get zero records.