Error opening database

[Steve Barnett]

I've developed a test application on my PC that uses the JET Engine. The
connection string is very basic and is constructed as follows:
connectionString = String.Format("Provider=Microsoft.Jet.OLEDB.4.0;Data
Source='{0}'", modelName);

On the development PC, this works fine. On a test PC, I get a message:
The format of the initialisation string does not conform to
specification starting at index 33

Since the same string works on the development PC, I'm taking this to mean
that there are missing drivers on the target PC. I thought I could sort this
by installing MDAC 2.8, but when I went to the downloads site, it explicitly
says that JET and OLEDB aren't included.

What do I need to get installed to be able to open my database? Or am I
wrong and there is a format error?

Thanks
Steve

 

[Michael Nemtsev]

Hello Steve,

try to download previous version of MDAC.
They remove old drives from one of 2.x version

SB> I've developed a test application on my PC that uses the JET Engine.
SB> The
SB> connection string is very basic and is constructed as follows:
SB> connectionString =
SB> String.Format("Provider=Microsoft.Jet.OLEDB.4.0;Data
SB> Source='{0}'", modelName);
SB> On the development PC, this works fine. On a test PC, I get a
SB> message:
SB> The format of the initialisation string does not conform to
SB> specification starting at index 33
SB> Since the same string works on the development PC, I'm taking this
SB> to mean that there are missing drivers on the target PC. I thought I
SB> could sort this by installing MDAC 2.8, but when I went to the
SB> downloads site, it explicitly says that JET and OLEDB aren't
SB> included.
SB>
SB> What do I need to get installed to be able to open my database? Or
SB> am I wrong and there is a format error?
SB>
SB> Thanks
SB> Steve
---
WBR,
Michael Nemtsev :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

 

[Morten Wennevik]

Hi Steve,

I'm not sure if this is applicable, but there seems to be a bug regarding
'' in connection strings.

http://support.microsoft.com/kb/823679/

If you are using .net 1.1 and have installed the service pack, it might be
worth checking if the target machine is patched as well.

 

[Steve Barnett]

Thanks, but it's .Net 2 (sorry, should have said that up front). I think
I'll need to knock up a test program to see exactly what the connection
string is. From what I've read, there is nothing I need to install to get
ADO.Net and the OLEDB drivers other than the framework itself, so it has to
be a format problem caused by the location of the database.

This is my first database app using any variant of ADO, so connection
strings are a foreign language to me. The "good old days" of DAO are much
more my experience, where you never had such problems!

Thanks
Steve

 

[Steve Barnett]

Actually, you were closer than I thought. The damn user had put the file in
a folder with a single quote in the path. That's the last time I throw
together a WIP demo of an app!

Thanks
Steve

Thanks, but it's .Net 2 (sorry, should have said that up front). I think
I'll need to knock up a test program to see exactly what the connection
string is. From what I've read, there is nothing I need to install to get
ADO.Net and the OLEDB drivers other than the framework itself, so it has
to be a format problem caused by the location of the database.

This is my first database app using any variant of ADO, so connection
strings are a foreign language to me. The "good old days" of DAO are much
more my experience, where you never had such problems!

Thanks
Steve