Provider Error On Deployment 1

[Guest_imported]

I created an installation package on my machine which has Visual Stuio 6.0. I ran set-up and installed it on another machine without VS. Setup went fine. However when I try to run the application, I get the following error:

Run Time Error 3706
Provider cannot be found. It may not be properly installed.

In my ado connection, I am using the Microsoft.Jet.OLEDB.3.51 Provider
Does anyone know what this means?

Thanks

 

[dellyjm]

Are you sure that that version of Access is on the client machine? [sig][/sig]

 

[Guest_imported]

That version of Access was on the clients machine.

 

[waynea]

I'm having the exact same problem, and here's what I've found, although I still don't have the answer:
If I install the Visual Studio on another machine (I've tried three so far), then package the app from there, it will install and run - ON THAT MACHINE. But take it to the intended target machine and it still will not run after installation. There must be some piece that's installed with the VS that is not being included by the P&D Wizard, but I have no clue what it is, as the app I'm working on is about as basic as you can get, and the P&D Wizard lists everything I can think of the should be required. By the way, the last machine that I tried doesn't have Access on it, but the program ran after being compiled and packaged on it. [sig][/sig]

 

[waynea]

Try this: check your list of references for the project to see if any are referencing a location inside \Program Files\Microsoft Visual Studio\. Unless the installation procedure builds this directory path, this could be the problem. [sig][/sig]

 

[dellyjm]

if it's a win95/98 machine did you run DCOM95 before installing it?

Delton. [sig][/sig]

 

[waynea]

You may have already found the answer, but:
I had this same problem, and found the following DLLs missing:
c:\program files\common files\system\oledb\MSJTOR35.DLL
c:\windows\system\MSJT4JLT.DLL

The way I found this was by running the dependency walker on both machines and comparing the outputs.