Q+E Err Msg: Column of Type (char) Does Not Allow Nulls

 Last reviewed: November 3, 1994
Article ID: Q78769
Summary:

An inappropriate error message may occur when you try to edit an SQL Server data table and the primary field is blank or contains a single space.

You will get the following error message printed twice in a Q+E dialog box: 

   Column of type (char) does not allow nulls. It may not be compared
   with null.
To edit the field, a value must be placed in the field using a form of a SQL Query. If the field is initialized by the SQL Server as full of blanks, this will also keep Q+E from getting this error message.

Microsoft has confirmed this to be a problem in Q+E version 3.0. We are researching this problem and will post new information here as it becomes available.

More Information:

The error that is generated relates to the fact that you cannot query a text field where the value is null. When Q+E begins to edit the record, it seems to be accessing the specific record where the primary field is equal to the field it is editing. In this case, the primary field is null and SQL Server is unable to process the query.

A similar error message occurs when you try to add a condition such as My_field equals null. In that case, the error message is appropriate.

Reference(s):

"Q+E for Microsoft Excel User's Guide," version. 3.0, page 33-36

KBCategory: kbother
KBSubcategory:

Additional reference words: 3.00

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: November 3, 1994
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.