Workgroup file information file error: OleDB to Access file

[Paul Keister]

I'm trying to open an Access database using OleDb. The database opens fine,
but when I try to open the database using a workgroup file with a name and
password, I always get the same error:

"Cannot start your application. The workgroup information file is
missing or opened exclusively by another user"

I gather that this means that OLEDB cannot open the workgroup file for some
reason. I've tried test workgroup files generated by both Access 2003 and
Access 2000, but always the same error. Please note the the database is NOT
password protected. So using "Jet OLEDBatabase Password" shouldn't be
necessary in this case. Here is the connection string I'm using:

Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\ThePath\TheDb.mdb;Jet
OLE DB:System Database=C:\The Path\WorkgroupTest.mdw;User ID=Me;Password=nyb

As an experiment, I tried to open the same database on the same sytem using
VB6 and ADO, and got the same error. The test workgroup files and database
are usable with Access.

Any thoughts on this would be welcome.

Paul Keister
http://www.pjpm.biz

 

[Paul Clement]

¤ I'm trying to open an Access database using OleDb. The database opens fine,
¤ but when I try to open the database using a workgroup file with a name and
¤ password, I always get the same error:
¤
¤ "Cannot start your application. The workgroup information file is
¤ missing or opened exclusively by another user"
¤
¤ I gather that this means that OLEDB cannot open the workgroup file for some
¤ reason. I've tried test workgroup files generated by both Access 2003 and
¤ Access 2000, but always the same error. Please note the the database is NOT
¤ password protected. So using "Jet OLEDBatabase Password" shouldn't be
¤ necessary in this case. Here is the connection string I'm using:
¤
¤ Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\ThePath\TheDb.mdb;Jet
¤ OLE DB:System Database=C:\The Path\WorkgroupTest.mdw;User ID=Me;Password=nyb
¤
¤ As an experiment, I tried to open the same database on the same sytem using
¤ VB6 and ADO, and got the same error. The test workgroup files and database
¤ are usable with Access.
¤
¤ Any thoughts on this would be welcome.


Any chance the files are read-only or you don't have the appropriate permissions to open the
database? I'm assuming that this is a VB.NET app and not an ASP.NET app.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)

 

[Paul Keister]

Any chance the files are read-only or you don't have the appropriate
permissions to open the
database? I'm assuming that this is a VB.NET app and not an ASP.NET app.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)

Yes, this is a .NET app, not and ASP.NET app. It's actually C#.NET. This
is a good thought, but this was not the problem. Here's what's wrong:
there's a typo in the connection string. It should be, "OLEDB:System
Database," not, "OLE DB:System Database." Doah!

I'm glad nobody noticed this. I feel dumb enough already. This is further
confirmation of one of my long-standing theories: the worst bugs are caused
by the dumbest mistakes. In other words, if you find yourself spending
hours on a problem, don't look for subtle explanations, look for glaring
errors!

Thanks for taking a look at this.

Regards,

Paul

 

[Paul Clement]

¤ ¤ >
¤ > Any chance the files are read-only or you don't have the appropriate
¤ > permissions to open the
¤ > database? I'm assuming that this is a VB.NET app and not an ASP.NET app.
¤ >
¤ >
¤ > Paul ~~~ (e-mail address removed)
¤ > Microsoft MVP (Visual Basic)
¤
¤ Yes, this is a .NET app, not and ASP.NET app. It's actually C#.NET. This
¤ is a good thought, but this was not the problem. Here's what's wrong:
¤ there's a typo in the connection string. It should be, "OLEDB:System
¤ Database," not, "OLE DB:System Database." Doah!
¤
¤ I'm glad nobody noticed this. I feel dumb enough already. This is further
¤ confirmation of one of my long-standing theories: the worst bugs are caused
¤ by the dumbest mistakes. In other words, if you find yourself spending
¤ hours on a problem, don't look for subtle explanations, look for glaring
¤ errors!
¤

I have to admit I missed it too and syntax was the first thing I looked for. ;-)


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)