PRB: ODBC Error When Updating an Edited Record

 Last reviewed: December 11, 1997
Article ID: Q166882
The information in this article applies to:
  • Microsoft Visual Database Tools, version 1.0

SYMPTOMS

The following error occurs in the Query Designer when you move off an edited table record: 

   ODBC Error: Client Cursor: 12 - No key columns are specified for the
   update table.

CAUSE

In the Query designer, a table must have a key column specified so that you can edit the table data. The Query Designer uses SQL "Update ... Where" syntax to update the record and requires a key field in the Where clause to uniquely identify the record.

RESOLUTION

Specify a key column in your table. See the InfoView topic titled “Defining a Primary Key” under “Microsoft Visual Database Tools, Database Designer, Working with Database Objects, Constraints”

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Create a new table.
2. Save the table. 3. Open the table. 4. Add a new record to the table. 5. Move off the record you just added. 6. Go back and edit a field in the new record. 7. Move off the record. The error message described above appears.

REFERENCES

For the latest Knowledge Base articles and other support information on Visual InterDev and Active Server Pages, see the following page on the Microsoft Technical Support site: 

   http://support.microsoft.com/support/vinterdev/


Keywords          : kbDtQDesigner
Version           : 1.0
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: December 11, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.