Connection string not working when deployed...

[lidds]

I have written a VB6 application that connects to an MS Access database using the following connection string:

myConnStr = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & myFilePath & ";"

This works fine on the computer that has Visual Studio 6 installed on it but when I deploy this to a test machine it gives me an error when trying to connect to the database. I think it must be something to do with it not finding the provider?

Both my test and development machine are Windows 7 x64 and both have up to FrameWork 4.0

Any ideas?

Thanks

Simon

[Doogle]

Did you use an Installation package to deploy on the other machine?
Has the other machine got Access installed?
What is the error message?
Have you put the Database into whatever myFilePath is?

[lidds]

I did install using an installer for the .Net part of my application, however for the VB6 exe I just added this to the installer as all dependencies should be install on Windows 7 to allow VB6 app to run?

This is the error:
http://www.ticodi.com/downloads/access_error.png

I have checked the myFilePath and the database does exit in the path.

The error is appearing when I execute the cnn.open command:

Dim Cnn As New ADODB.Connection
Dim myConnStr As String

myConnStr = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & myFilePath & ";"
Cnn.Open (myConnStr)

Thanks

Simon

[DickGrier]

Does UAC permit you to access this path from your program? Some file paths may require administrator rights. Make sure that your program has access. One way to check is to right-click the exe and select "Run as Administrator" from the drop-down menu. Make sure that the target path is one where your program can run as a simple User.

Dick

[Magic Ink]

It could be that the contents of myFilePath are not causing the problem however can you please supply its exact contents when it fails.

[dilettante]

There are other stabs in the dark at answers at the other sites this question was cross-posted to.

[Magic Ink]

And nobody knows what myFilePath contains yet!

[dilettante]

Exactly.

My guess is it fails because the file name has spaces, or may even be based on App.Path and ends up having "Program Files (x86)" within it. Simply adding quotes would take care of it, and in this case even apostrophes (') will work.

Then UAC and file virtualization will probably be his next stumbling block.

Or we could be all wet and the problem is somewhere else.

The use of redundant parens on the .Open call and that trailing semicolon in the connection string don't bode well. There may be other time bombs in his code.