PRB: "Error 1709" When Several Users Are Using the Same Database

 Last reviewed: July 2, 1997
Article ID: Q170917
The information in this article applies to:
  • Microsoft Visual FoxPro for Windows, versions 3.0, 3.0b, 5.0, 5.0a

SYMPTOMS

When an application is being accessed by several users in a multi-user environment, the following error might occur when the database container is being manipulated: 

   Error 1709 - Database object is being used by someone else.
If you issue a RETRY command, it resolves the error message.

CAUSE

Two or more users are momentarily accessing the database container in a way that will not allow processing the information at the same time even though the database container is shared. The first user's information is processed and the second user receives the error. The chances of two or more users triggering this error is very slim. Therefore, this error occurs randomly. When this error does occur, the program needs to retry the task for the second user.

RESOLUTION

By setting up an error routine to trap this error and then issuing a RETRY command you will eliminate this problem. Below is a sample ON ERROR routine. Place the following code in a prg called onerror.prg: 

   PARAMETERS errnum

   DO CASE errnum = 1709
      RETRY
   ENDCASE
At the start on the application, place the following command: 

   ON ERROR DO onerror.prg WITH ERROR()

STATUS

This behavior is by design.

Keywords : vFoxWin
Version : WINDOWS:3.0,3.0b,5.0,5.0a
Platform : WINDOWS
Issue type : kbprb

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.