Hi Alan,

Does your application uses another shared DBC iin addition to the local one? It seems that any shared object in the DBC could cause this error, not just views.

>I have an application (VFP6 front-end with SQL backend using remote views and SQLPT) and users are getting the error message "Database object is being used by somone else" (error 1709).
>
>As suggested by previous answers to this problem, each workstation is using a local copy of the .dbc containing remote view definitions. This has considerably reduced occurrance of the error, but it is still happening.
>
>In my baseform error handler, I have trapped error 1709, introduced a small delay (0.3 sec), then perform a RETRY. If the .dbc is still locked, the error-handler should be called again, and so on, but no error message should be displayed. (Question - if the form calls a .prg (or a procedure/function in a .prg) in which an error occurs, does the form.error() event kick-in, or the error-handler associated with the .prg file?)
>
>Are there any other reasons why this error could still be occurring?
>