Mix of DAO(VB3) and ADO(VB6) and Acc2.0 and Access2003 on XP SP2

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I fire up an old VB3 app that hits an Access 2.0 db. Fine.
Then fire up a VB6 app that hits that 2.0 db via ADO to an Access 2000 db.
That 2000 db has native tables and one link to a table in the 2.0 db.
The SQL uses that link to 2.0 in a join.

The 2.0 file is on the server (w2000), the 2000 db is local (XP)

If that VB3 app is open, the VB6 connection gives "cannot connect, db in use",
referring to the 2.0 file on the server.

I've been developing for 15 yrs, mostly in these technologies, including
SQLSrvr & Oracle etc. This is the biggest stumper yet.

In short, in VB6, ADO is trying to connect to an Acc2000 db with a link to a
table in Acc 2.0. It fails if the VB3 app is open. (I can hit native tables
in the acc2000 db though).

I've fiddled with network permissions, MDAC, JET. I've converted the 2.0 to
2000.
Still fails. I've converted everything to everything else and back. I've
tried just about everything I can come up with.

I can re-write the code and use two connections and two recordsets for sure,
yes.
That's my solution now. But that will take more time and I don't have it
(deadline on other project).

Am I missing something?

We're re-writing the whole system but have to live a year with this old mess.
If I can make this pblm go away, my boss will LOVE me.

If anyone can help out, you'll be my hero.

70 hour week, a little goofy now.

Thanks.
 
Hi.
If that VB3 app is open, the VB6 connection gives "cannot connect, db in use",

I've fiddled with network permissions
Click to expand...

Do all users who are going to open these Access databases have "Full
Control" Windows security permissions on the directories where these Access
databases are located?

Is there a workgroup information file (*.MDW) in the same directory as any
of the databases with the same base name (such as MyData.MDW with
MyData.MDB)? If so, could anybody be actively joined this workgroup file
when someone is attempting to connect to the Access databases?

Is there a locking database file (*.LDB) in the same directory with the same
base name as the Access database, which no one seems to be able to delete,
even when no one has the database open?

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
Thanks Camaro (I'm a 'Stang man, but can be persuaded)

Let me check and re-verify what you have mentioned. I also pulled your article
from QBuilt - net site - great article. Let me study it and fool around some
more
and I'll get back. Thanks for the response - new stuff here for me.
 
You're welcome. Hopefully there's information in the article that will help
alleviate the locking problem. If not, post back and we'll try to offer
other suggestions.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
OK. I opened up all permissions on shares and folders to God level.
Same problem.

Then I wrote a small test app to get to the core.

Have VB3 dao app and a VB6 ADO app hitting trying to open same Access 2.0
file on a network share.

TEST: Open VB3 app and establish conn to mdb file. Fine. Thennopen VB6 and
get conn and then close connection. Any subsequent VB6 attempts to open that
mdb (while VB3 still has it) fails. Other VB3 attempts succeed.

A little more testing and voila.

SOLUTION: I wrote a little util. Does nothing but grab a vb6 ado conn to the
file and holds it all day long. As long as a VB6 ADO conn hits first (creates
ldb file), users can hit that ACC 2.0 file all day with VB3 or VB6 as much as
they want. Seems logical and it works.

Thanks for your help. I learned a lot about the matrix of permissions in XP
so it was worth it.

Take Care,

Tristan
 
Back
Top