Skip to Main Content

DevOps, CI/CD and Automation

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Connectivity to Oracle via ADO & OraOLEDB using Visual Basic 6

393676May 1 2003 — edited May 5 2003
I have an application I’ve developed using Visual Basic 6.0 that accesses an Oracle database using something similar to the following code:

Public db As Connection
Set db = New Connection
db.Open "PROVIDER=OraOLEDB.Oracle;Data Source=my_sid;User ID=usr;Password=pwd"

Dim rs As Recordset
Set rs = New Recordset
rs.Open ConvertSQL("SELECT FIELD_1 FROM TABLE_1"), db, adOpenStatic, adLockReadOnly, adCmdText

Do Until rs.EOF
Debug.Print rs("FIELD_1").Value
rs.MoveNext
DoEvents
Loop

Obviously this is not my real application but this should convey the methods that I’m using to access the DB. My implementation works flawlessly on my development computer with the Oracle Provider for OLE DB 9.2.0.1.0 drivers installed but when I try to install my application on a clients machine I have nothing but problems. Before I go into how I’m deploying it on client machines, which are Windows NT4, 2000 and XP let me first ask a basic question, like what should I have on the client machine to get this to work. To my knowledge I need the application, MDAC drivers and Oracle drivers. The Oracle driver part is where I’m a little confused because as I see it I have two options.
1. Use the Package & Deployment Wizard and let it find all the related drivers and add them to the install package.
2. Install the OLEDB drivers on each client machine manually before I install my application.

I have tried both of these options with no success. With option one I received several messages stating that a certain driver cannot be installed and when I examined the package I found that that driver was not included in the package. I have gone through this several times each time adding the driver that is missing, but now I receive the error “An error occurred while registering the file C:\WINNT\system32\OraOLEDBus.dll” but this file is included in the package so I’m not sure what it wants. With option two is this really necessary, it seems like it installs a lot of extra stuff and I would rather not install anything that I’m not using on the clients machine. With either option what about the tnsnames.ora file do I need this on the clients machine and if so where do I put it?

Any light you can shed on this subject would be greatly appreciated.
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jun 2 2003
Added on May 1 2003
3 comments
1,421 views