Q+E Err Msg: Command Has Been Aborted

Last reviewed: November 2, 1994
Article ID: Q66670

SUMMARY

If you attempt to add or modify data in a field in a SQL Server table that has had rules applied to it, the "Command Has Been Aborted" error message may be generated if the data entered does not meet the requirements of the rules.

MORE INFORMATION

SQL Server allows rules to be defined for fields in a table. A rule sets up criteria that the data entered in that field must satisfy.

Q+E does not support creating rules and preexisting rules cannot be viewed from Q+E. However, Q+E will verify that the data you enter matches preexisting rules.

The following is an example of a rule that applies from a SQL Server front end that supports adding rules:

CREATE rule pub_idrule

       as @pub_id like "99[0-9][0-9]"

This example places the restriction on the field pub_id that values entered must start with "99" and contain four digits. "9954", "9900", and "9999" (without the quotation marks) would be valid entries.

Entering "8056" in the field pub_id from Q+E would cause the "Command Has Been Aborted" error.

KBCategory: kbother
KBSubcategory:

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