PRB: "Record in Use Cannot Write" with @ ... SAY ... VERB

 Last reviewed: June 26, 1995
Article ID: Q117708
The information in this article applies to:
  • Microsoft FoxPro for Windows, versions 2.5, 2.5a, 2.5b, 2.6

SYMPTOMS

When you are using the @ ... SAY <general field> VERB 0 command to update an OLE object in a database file that was opened as shared, the error message "Record in use cannot write" will occur when you return to FoxPro from the server application after choosing Update.

WORKAROUNDS

There are two workarounds to this problem:

  • Open the table exclusively.

    -or-

  • Use the MODIFY GENERAL command. When the general field comes up, press ENTER or double-click the mouse button to activate the server program. When you return to FoxPro, the general field will be updated.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Open a table with a general field shared and browse it.

  2. Insert a Paintbrush object in the general field and close the Browse window.

  3. From the Command window, issue the following command, replacing <general field> with the name of the general field: 

          @ 1,1 SAY <general field> VERB 0

  4. Modify the Paintbrush object.

  5. From the File menu in Paintbrush, choose Exit And Return To FoxPro.

The "File in use cannot write" error will appear when Paintbrush closes and you return to FoxPro.

Additional reference words: FoxWin 2.50 2.50a 2.50b 2.60 ole errmsg err msg
object
linking and embedding
KBCategory: kbole kbprg kberrmsg kbprb
KBSubcategory: FxinteropOle

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: June 26, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.