I've run into this problem when retrieving the view definition from the DBC. I've always kept views in their own DBC, so the solution was simple--create the DBC on each user's hard drive when they start up the app. It's quite easy to do in code. I've got an online paper that covers how to do this at www.peisch.com/downloads.html. (Look for Views.zip)

>I have come across a known multi user problem with VFP which is:
>
>When 3 or more users try to open the same form at exactly the same time the following error is generated:
>
>Error 1709 - database object is being used by someone else.
>
>
>Microsoft, (in their MSDN article Q170917) say that this error is by design, Ha.
>
>The resolution suggested is to capture the error immediately and RETRY.
>
>I have done this but the RETRY does not attempt to open the database again being that it initial failure occured while it was automatically opening the dataenvironment ( as per Dataenvironment.AutoOpenTables = .T.).
>
>The RETRY gets rid of the 1709 error message BUT DOES NOT re-attempt to open the database as it should do. Consequently, none of the tables/views get opened.
>
>If I wrote code to open all my tables, then I suspect the RETRY would work. However, I have over a 150 forms and do not have the time to write code to open all the remote views in the Dataenvironment.OpenTables method.
>
>Has anyone else overcome this problem, leaving the datenvironment in tact?