BUG: CREATE CURSOR Does Not Accept UNIQUE as a Field Name

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

SYMPTOMS

When using the CREATE CURSOR command, the name UNIQUE may not be used to name one of the fields in the cursor. The error message "syntax error" is generated by issuing the CREATE CURSOR command from either the Command window or from a compiled program file when UNIQUE is used as a field name.

The following example generates this syntax error: 

   CREATE CURSOR address (cName C(20), UNIQUE C(20))
UNIQUE was allowed as a field name prior to Visual FoxPro version 3.0 when used in the CREATE CURSOR command.

CAUSE

UNIQUE is a reserved word in Visual FoxPro. However, reserved words can be used in the CREATE TABLE/CURSOR commands by using name substitution.

RESOLUTION

The following example uses name substitution to work around this problem. In this example, UNIQUE can be used as a field name in the CREATE CURSOR command. 

   CLOSE DATABASES
   CLEAR
   cField = "UNIQUE"
   CREATE CURSOR employee (cName C(20), (cField) C(20))
   DISPLAY STRUCTURE
Notice that once the DISPLAY STRUCTURE command is issued, a cursor structure is displayed that contains two fields: cName and UNIQUE.

STATUS

Microsoft 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.

Keywords : buglist3.00 buglist3.00b buglist5.00 FxprgTable VFoxWin vfpbug5.0a kbbuglist
Version : 3.0 3.0b 5.0 5.0a
Platform : WINDOWS
Issue type : kbbug

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: May 6, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.