Problem with Connection String and Workgroup Information File

Problem with Connection String and Workgroup Information File

Post by CommanderDat » Mon, 24 Jun 2002 16:56:14



I am using VB6 (SP5) as a front-end to an Access 2000 database.  I can
happily create connection strings in code using the Jet 4.0 OLEDB provider,
and open up recordsets to access the Access 2000 database.  However, when I
try to use an ADO data control and compose a connection string using its
property pages I cannot test the connection successfully.  It gives me an
error about Workgroup Information File missing or in exclusive use by
another user.

I don't think the problem is with the SYSTEM.MDW file because, as stated, I
have no problem with programmatic connection strings.

Any ideas?

Rgds
Daisy

 
 
 

Problem with Connection String and Workgroup Information File

Post by John Blessin » Mon, 24 Jun 2002 18:21:04



Quote:> I am using VB6 (SP5) as a front-end to an Access 2000 database.  I can
> happily create connection strings in code using the Jet 4.0 OLEDB
provider,
> and open up recordsets to access the Access 2000 database.  However, when
I
> try to use an ADO data control and compose a connection string using its
> property pages I cannot test the connection successfully.  It gives me an
> error about Workgroup Information File missing or in exclusive use by
> another user.

> I don't think the problem is with the SYSTEM.MDW file because, as stated,
I
> have no problem with programmatic connection strings.

> Any ideas?

> Rgds
> Daisy

Are you specifying a username/password other than admin/blank?

--
John Blessing
http://www.LbeHelpdesk.com - Home of the free helpdesk software

 
 
 

Problem with Connection String and Workgroup Information File

Post by CommanderDat » Mon, 24 Jun 2002 21:00:52


Good question and sorry you had to force it out of me!  The database is
password-protected.  I specified the password in the programmatic connection
string without a problem.  Been trying to use the same password in the
password box of the property page.  Username is admin.  What am I doing
wrong?

Rgds
Daisy


Quote:> Are you specifying a username/password other than admin/blank?

 
 
 

Problem with Connection String and Workgroup Information File

Post by CommanderDat » Mon, 24 Jun 2002 21:08:06


In addition to resolving my problem as initially stated, may I also ask
exactly what is the relationship of the Workgroup Information File and VB /
Access?  As an experiment, I renamed the WIF temporarily and see if I could
open the database using Access.  Access couldn't.  I then tried to open the
database in VB using my programmatic connection string and it could!  So it
seems as if the WIF is not essential for VB to open an Access database
anyway...  Does this mean I don't have to redistribute the SYSTEM.MDW when
redistributing my VB application?

Sorry for so many questions.

Rgds
Daisy




> > I am using VB6 (SP5) as a front-end to an Access 2000 database.  I can
> > happily create connection strings in code using the Jet 4.0 OLEDB
> provider,
> > and open up recordsets to access the Access 2000 database.  However,
when
> I
> > try to use an ADO data control and compose a connection string using its
> > property pages I cannot test the connection successfully.  It gives me
an
> > error about Workgroup Information File missing or in exclusive use by
> > another user.

> > I don't think the problem is with the SYSTEM.MDW file because, as
stated,
> I
> > have no problem with programmatic connection strings.

> > Any ideas?

> > Rgds
> > Daisy

> Are you specifying a username/password other than admin/blank?

> --
> John Blessing
> http://www.LbeHelpdesk.com - Home of the free helpdesk software

 
 
 

Problem with Connection String and Workgroup Information File

Post by Paul Clemen » Wed, 26 Jun 2002 02:40:36


I am using VB6 (SP5) as a front-end to an Access 2000 database.  I can
happily create connection strings in code using the Jet 4.0 OLEDB provider,
and open up recordsets to access the Access 2000 database.  However, when I
try to use an ADO data control and compose a connection string using its
property pages I cannot test the connection successfully.  It gives me an
error about Workgroup Information File missing or in exclusive use by
another user.

I don't think the problem is with the SYSTEM.MDW file because, as stated, I
have no problem with programmatic connection strings.

See the following:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q191754


Microsoft MVP (Visual Basic)

 
 
 

Problem with Connection String and Workgroup Information File

Post by Jeff Johnso » Wed, 26 Jun 2002 08:57:43



Quote:> Good question and sorry you had to force it out of me!  The database is
> password-protected.  I specified the password in the programmatic
connection
> string without a problem.  Been trying to use the same password in the
> password box of the property page.  Username is admin.  What am I doing
> wrong?

You're using the stupid "database password" feature of Access, that's what
you're doing wrong. I've seen it give people tons of problems. I highly
recommend using "real" Access security. Yes, it's complex to those who've
never used it, but it does work.
 
 
 

1. Problem opening a query in ACCESS through workgroup connection string

i have a following connection string which is perfectly fine and i can
successfully access to the ACCESS database through workgroup
connection string.

"Provider=Microsoft.Jet.OLEDB.4.0; Data
Source=C:\Shared\NetAccessDatabase\Net.mdb;user
id=SYSTM;Password=tmsa;Jet OLEDB:System
database=c:\Winnt\system32\system.mdw;"

once i have accessed to the ACCESS databae i have tried to open a
query called vtblDefaultSegment...The code for query
vtblDefaultSegment is as follows:

 SELECT [IDSegment]
FROM tblTMSGroups
WHERE GroupID=SYSTM;

 when i do this i should get one record back but instead i get an
error messaga saying "No value given for one or more required
parameters"...I would really appreciate if some one could really help
me with this...Seems like i couldn't open the query
vtblDefaultSegment..Thanks

2. Changing a Connection in a ADP file

3. Problem Replicating SQL Server 2000 Database With Access 2000 Database With Workgroup Information File

4. How to restore database access after restrong the database?

5. Workgroup Information File

6. db_file_multiblock_read_count

7. Workgroup information file missing?

8. Forms 4.5 Item Validation Question

9. Workgroup Information File

10. Please Help re Code OK in VBA, not in VB re Workgroup Information File

11. Workgroup Information File Missing message.

12. Workgroup Information Files

13. Access workgroup information file Lost