BUG: Alter Table Within a Stored Procedure Causes Msg 1750

Last reviewed: May 5, 1997
Article ID: Q155767

The information in this article applies to:

Microsoft SQL Server, version 6.0

SYMPTOMS

When a stored procedure adds a constraint to an existing table using the alter table statement, the following error message appears:

   [INTERNAL ERROR] unable to locate original param in voidptr list.
   Msg 1750, Unable to create constraint

NOTE: This problem does not occur if alter table is the only command within the procedure text. A simple If condition, such as “if @@error,” following the alter table statement causes the problem to occur.

WORKAROUND

Declare a local variable and assign the alter table statement to the variable. Use the Exec statement for execution.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: TABLE INTERNAL ERROR
Keywords : kbbug6.00 kbnetwork SSrvStProc
Version : 6.0
Platform : WINDOWS

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