INF: Why dbqual() Returns Null WHERE Clause in Browse Mode

Last reviewed: April 25, 1997
Article ID: Q45263

The information in this article applies to:

Microsoft SQL Server Programmer's Toolkit, version 4.2

If the specified table does not have a unique index (or primary key) and timestamp, dbqual() will return a null WHERE clause. Dbtabbrowse() indicates whether or not a table can be updated using dbqual().

If dbtabbrowse() returns true for the table, and dbqual() still returns a null WHERE clause, you need to verify that the TIMESTAMP column is not null. This situation can occur if a timestamp column is added to a table with an ALTER statement after the table was created. A simple update such as "UPDATE TableX set ColA = ColA" will ensure that the TIMESTAMP in every record contains a value.

Additional query words: DB-Library DB-Lib dblib
Keywords : kbprg SSrvDB_Lib
Version : 4.2
Platform : OS/2

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