Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Could Not Locate Provider

Status
Not open for further replies.

morechocolate

Technical User
Apr 5, 2001
225
US
I apologize in advance if this posting is already out there, but Keyword search is not active and there are too many posts to look through.

That being said my question is this. I created an executable (not a package). The executable uses an ADO connection to Access 97(Provider=Microsoft.Jet.OLEDB.3.51).

The executable is now on the server, but an error occurs stating something to the fact that it could not locate the provider. I run this same program on my desktop an it runs fine. Of course, there is one major difference, I have Access on my desktop and the server does not have Access, according to the guy who ran the program. That I do not understand because we have other programs that write data to Access Databases.

The only thing I could thing of is that I need to install the program onto the server. Is that correct? If so, what would be need to be done so that the program can be part of a batch cycle?

Thanks.

By the way, there are some other programs on the same server that use DAO. The code is as follows:

Global dbHoldTrad As Database
Global Const tbHoldTable = "HoldTrad"
Global rsHoldTrad As Recordset

Then there is a routine with:

Set dbHoldTrad = OpenDatabase(strOutDBName)
Set rsHoldTrad = dbHoldTrad.OpenRecordset(tbHoldTable)

This I am told works fine.

Thanks for your help.

pam
 
You need to install an Access database on the server that you are running your executable on. If several people are going to access this database the executable needs to point to that database on the server. That should correct your problem.
 
It looks like your server has the DAO components, but not the ADO components. I think that you have 2 options. You can download the MDAC from microsoft and install on the server, or use the Package and Depolyment wizard to distribute the application. Using the install package will insure that the proper components are included. Maybe there is more missing than the mdac components. This is the better choice.
David Paulson


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top