By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,960 Members | 2,232 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,960 IT Pros & Developers. It's quick & easy.

Error opening database

P: n/a
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;Da ta
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
Sep 30 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Hello Steve,

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

SBI've developed a test application on my PC that uses the JET Engine.
SBThe
SBconnection string is very basic and is constructed as follows:
SBconnectionString =
SBString.Format("Provider=Microsoft.Jet.OLEDB.4.0; Data
SBSource='{0}'", modelName);
SBOn the development PC, this works fine. On a test PC, I get a
SBmessage:
SBThe format of the initialisation string does not conform to
SBspecification starting at index 33
SBSince the same string works on the development PC, I'm taking this
SBto mean that there are missing drivers on the target PC. I thought I
SBcould sort this by installing MDAC 2.8, but when I went to the
SBdownloads site, it explicitly says that JET and OLEDB aren't
SBincluded.
SB>
SBWhat do I need to get installed to be able to open my database? Or
SBam I wrong and there is a format error?
SB>
SBThanks
SBSteve
---
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
Sep 30 '06 #2

P: n/a
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.
--
Happy Coding!
Morten Wennevik [C# MVP]
Oct 2 '06 #3

P: n/a
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
"Morten Wennevik" <Mo************@hotmail.comwrote in message
news:op***************@tr024.bouvet.no...
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.
--
Happy Coding!
Morten Wennevik [C# MVP]

Oct 2 '06 #4

P: n/a
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

"Steve Barnett" <no****@nodomain.comwrote in message
news:Oh*************@TK2MSFTNGP06.phx.gbl...
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
"Morten Wennevik" <Mo************@hotmail.comwrote in message
news:op***************@tr024.bouvet.no...
>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.
--
Happy Coding!
Morten Wennevik [C# MVP]


Oct 2 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.