Microsoft KB Archive/175090
Article ID: 175090
Article Last Modified on 5/2/2006
- Microsoft Visual InterDev 1.0 Standard Edition
This article was previously published under Q175090
The following error occurs when previewing an Active Server Pages (ASP) page that calls an Oracle stored procedure:
The conditions that cause this error are as follows:
- Making a call to an Oracle stored procedure.
- Using the Data Command Control to insert the ActiveX Data Objects (ADO) code that accesses the stored procedure.
- Editing and closing the Data Command Control at least once after initially inserting the control.
- Choosing the stored procedure name from the Command Text drop-down list box in the Data Command's property sheet.
The Data Command Control incorrectly parses the Command Text being assigned to the cmdText object. The second time the DataCommand Control is opened it parses the sting as follows:
cmdTemp.CommandText = 'dbo.''my_stored_proc'''
Which should be the following:
cmdTemp.CommandText = 'dbo.my_stored_proc'
- Open the Data Command Control.
- Manually enter your stored procedure name (for example, "my_stored_proc") in the Command Text property box.
- Close the control and preview the page.
- It works. If you open the control again and close it, it still works.
Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
Steps to Reproduce Behavior
- Open or create a Visual InterDev project.
- Add a data connection to an Oracle database.
- Add a new ASP page to the project.
- Insert a Data Command Control.
- Choose the data connection created in step 2 above from the Data Connection drop-down list box.
- Choose "Stored Procedure" from the "Command Type" drop-down list box.
- Choose one of the stored procedures available to your database from the Command Text drop-down list box.
- Save and preview the ASP file.
For the latest Knowledge Base articles and other support information on Visual InterDev and Active Server Pages, see the following page on the Microsoft Technical Support site:
Keywords: kberrmsg kboracle kbide kbprb KB175090