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.
> > 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
> > and open up recordsets to access the Access 2000 database. However,
> > 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
> > 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
> > 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