The information in this article applies to:
SYMPTOMSIf an EXECUTE is attempted on a table instead of a stored procedure, the error message that should be returned is: However, the following error may be returned instead:
WORKAROUNDPrograms that rely on the error message should check for both messages. In ADO, a COMMAND object may be used to indicate that the object is a table and not a stored procedure. MORE INFORMATION
The following scenario illustrates the problem:
However, if User B (USERB) runs EXEC USERA.TABLEA, the error message returned may be: Programs that only test for one of the messages may not function correctly if the other message is returned. For example, the following ADO 1.0 code runs correctly under the user context of USERA, but may fail under the user context of USERB and returns the error: This is because under USERB, ADO first tests if USERA.TABLEA is a stored procedure by attempting to execute it. However, due to the EXECUTE permission denied error message, it concludes that USERA.TABLEA is a stored procedure, and does not continue on to test if TABLEA may be a table.
Additional query words: asp visual basic vb active data objects
Keywords : kbprg kbusage SSrvProg SSrvVisB |
Last Reviewed: December 14, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |