Microsoft KB Archive/814186

= BUG: &quot;Invalid Property Data&quot; Error While Creating OracleCommand in Visual Studio .NET 2003 =

Article ID: 814186

Article Last Modified on 5/20/2005

-

APPLIES TO


 * Microsoft Visual Studio .NET 2003 Academic Edition
 * Microsoft Visual Studio .NET 2003 Enterprise Architect
 * Microsoft Visual Studio .NET 2003 Enterprise Developer
 * Microsoft Visual Basic .NET 2003 Standard Edition
 * Microsoft Visual C# .NET 2003 Standard Edition

-





Beta Information
This article discusses a Beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this Beta product. For information about how to obtain support for a Beta release, see the documentation that is included with the Beta product files, or check the Web location from which you downloaded the release.



SYMPTOMS
When you create a command object for Oracle to run a stored procedure by using the OracleCommand object from the Toolbox, you may receive the following error message after you specify the stored procedure name in the CommandText property:

Invalid Property Data

The stored procedure “OraclePackageName.OracleProcedureName” could not be found in the database.



WORKAROUND
To work around this problem, use one of the following methods:
 * In the CommandText property of OracleCommand1, type the name of the stored procedure exactly as it appears (this property is case-sensitive) in the stored procedure list in Server Explorer.
 * Click OK to ignore the error message, and then manually add the code to call the Oracle stored procedure in your class.

You can view the name of the stored procedure in Server Explorer. To do this, follow these steps:
 * 1) On the View menu, click Server Explorer.
 * 2) Right-click Data Connection, and then click Add Connection.
 * 3) On the Provider tab, click to select the Microsoft OLE DB Provider for Oracle check box.
 * 4) Click the Connection tab.
 * 5) Type the , the   and the  , and then click Test Connection.
 * 6) Click OK to close the Test connection succeeded dialog box.
 * 7) Click OK to close the Data Link Properties dialog box.
 * 8) Expand Oracle database.
 * 9) Expand Stored Procedure to view the list of existing stored procedures.



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.



Steps to Reproduce the Behavior

 * 1) In Visual Studio .NET 2003, create a new Windows Application project using Visual Basic .NET or Visual C# .NET.
 * 2) On the View menu, click Toolbox, and then expand Data.
 * 3) Double-click OracleConnection. OracleConnection1 is created.
 * 4) Double-click OracleCommand. OracleCommand1 is created.
 * 5) Right-click OracleCommand1, and then click Properties.
 * 6) Click Connection, and then expand Existing. Click to select OracleConnection1.
 * 7) In the CommandType property, click StoredProcedure.
 * 8) In the CommandText, type the name of the stored procedure, and then press ENTER. You receive the error mesage that is described in the &quot;Symptoms&quot; section.

Note On the Do you want to regenerate the Parameters collection for this command? message box, click Yes.

