Microsoft KB Archive/170148

From BetaArchive Wiki

Article ID: 170148

Article Last Modified on 5/12/2003


  • Microsoft Visual FoxPro 3.0 Standard Edition
  • Microsoft Visual FoxPro 3.0b Standard Edition
  • Microsoft Visual FoxPro 5.0 Standard Edition
  • Microsoft Visual FoxPro 5.0a

This article was previously published under Q170148


You cannot trap duplicate key errors such as the following when the error is caused by a user's interaction with a grid on a form:

Uniqueness of index "name" is violated (Error 1884)


For a workaround that uses record buffering, place the following code in the Valid method of a TextBox of the Grid:

   *Invalid Primary Key Trapped here since Error method of Grid does not.
      RETURN 0


Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This has been corrected in Visual FoxPro 6.0.


Steps to Reproduce Behavior

  1. Issue the following two lines in the Command window:

          CREATE DATABASE primerr
          CREATE TABLE tblprim (fld1 c(3) PRIMARY KEY, fld2 c(2), fld3 c(3))
  2. Add several records to the above table.
  3. Create a new form by selecting New from the File menu.
  4. Select Form in the dialog box and click the New File button.
  5. When the form appears, right-click on the form to invoke the shortcut menu and click DataEnvironment.
  6. When the DataEnvironment window comes up, right-click in the window to invoke the shortcut menu and click Add Table.
  7. When the Open dialog box appears, select the table created in Step 1.
  8. Drag and drop the table from the DataEnvironment to the form to make a grid.
  9. Run the form and type in a duplicate value for a record in fld1 column and move off the record. Note that Visual FoxPro presents an error message.
  10. Click Revert and close the form.
  11. Modify the form.
  12. On the property sheet, select Grid from the drop down box at the top.
  13. Find the grid's Error method and add in a WAIT WINDOW command.
  14. Repeat step 9.

In version 3.0 and 3.0b, step 14 behaves exactly the same as it did when step 9 was executed.

Keywords: kberrmsg kbbug kbfix kbvfp600fix kbprb KB170148