>I have a problem with some clients that's driving me crazy for some time.
>
>I know, I know, I shouldn't use DBC with remote views but my application is built with it. We open all references tables in the default data environment. Then when a form is opened, we use the command VIEW... AGAIN. This is working great with much of our clients.
>But sometimes, with no particular reason, there is a view that cannot be opened. I got an "Error loading file when trying to open the view." The lock on the view is removed only when we quit the entire application. I am aware of the lock on the dbc when a form is opened and did the corrections for that. But even with a single user, the problem occurs...
>
>We are planning to switch to PASSTHROUGH but we have to live with remote views for the next few months... Does this happened to others???
>
>Thanks!

Do you use local DBC containers for the views? If you do not use local DBCs note that all your users compete for the views because VFP locks the record in DBC file that containes the view definition, when a user trys to browse (SELECT) it

HTH