Visual Basic Q&A

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.
Resolution
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: On the View menu, click Server Explorer.Right-click Data Connection, and then click Add Connection.On the Provider tab, click to select the Microsoft OLE DB Provider for Oracle check box. Click the Connection tab. Type the server name, the user name and the password, and then click Test Connection. Click OK to close the Test connection succeeded dialog box. Click OK to close the Data Link Properties dialog box. Expand Oracle database. Expand Stored Procedure to view the list of existing stored procedures.

Symptoms
When using DAO/Jet to access an Oracle database, you get either blank rowsback in a grid or rows filled with #DEFINE (when using Access).
Resolution
This behavior is caused by DAO having a problem determining the datatypefor Oracle columns defined as NUMBER.

Symptoms
After creating and saving a new view with the Data view tool, trying toaccess the newly created view results in the following run-time error:

‘-2147217865 (80040e37)’: ORA-00942: table or view does not exist.
Resolution
The Data View is saving the view name in lower case to the Oracle database,but Oracle sees views all in upper case.