BUG: Spell Checking on Memo Field Causes ErrorLast reviewed: April 25, 1997Article ID: Q163798 |
The information in this article applies to:
SYMPTOMSInvoking the Spell Checker on a Memo field in a multi-user situation will cause the following warning:
"Memo field could not be locked for Spell Checker"This warning occurs if the record is currently locked by another user.
CAUSEThe Spell Checker is ignoring the Optimistic Record Locking scheme of the Form.
RESOLUTIONPlace the following code in the DoubleClick Method of Edit Region:
&& Copy current record to a separate file to avoid locking problem COPY NEXT 1 TO spellchk.dbf USE spellchk IN 0 SELECT spellchk && The following line may be added if the user wants changes && made to the buffered data appearing in Spell Checker. The reason && for this is the COPY TO command is reading directly from dbf file && on disk rather than the buffered data appearing in Edit region. REPLACE spellchk.notes WITH THIS.VALUE && Run SpellChecker on the temporary table MODIFY MEMO notes NOWAIT DO (_SPELLCHK) CLOSE MEMO notes && Update Edit Region and original table with any changes made && by user/SpellChecker THIS.VALUE=spellchk.NOTES USE && Close the temporary table SELECT employee THIS.REFRESH() && Update the Edit Region && Erase the temporary files created ERASE spellchk.dbf ERASE spellchk.fpt STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATION
Steps to Reproduce Behavior
REFERENCESFor more information about spell checking in FoxPro, please see the following articles in the Microsoft Knowledge Base:
ARTICLE-ID: Q117212 TITLE : How to Use the FoxPro Spelling Checker (SPELLCHK.APP) ARTICLE-ID: Q136641 TITLE : PRB: Spell Checking Edit Box Contents Does Not Work |
Additional query words: 3.00 3.00b 5.00
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |