Hi, guys!

It happens in a single-user application? Probably, because different data sessions. In fact "AGAIN" option for "USE" command works only inside of the same data session. When you try to open the view in another data session, it just re-open it completely with running query to get data from table. As a result, when something is locked in data table, you will get such error. For example, in one data session you have view opened and modified + udated in transaction. This will lock the source table. When you then try to open exactly the same view in another data session (even with AGAIN option), query for view runs again and cannot get data because table is locked.

HTH.

>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!