Two ldbs for one mdb?

Two ldbs for one mdb?

am 12.10.2007 21:32:47 von Salad

A97

I have a database called DB1
My desktop icon properties open it like
C:\MSACCESS.EXE C:\Apps\DB1.MDB /wrkgrp C:\Apps\DB1.MDW

I then made a copy of DB1 called DB2
I changed the desktop icon proerties to
C:\MSACCESS.EXE C:\Apps\DB2.MDB /wrkgrp C:\Apps\DB1.MDW

So they both used DB1.MDW.

I was running some test code but I discovered that my LDB was DB1.LDB
when I opened DB2. I figured it would create one called DB2.LDB. So I
thought, create a DB2 mdw. So the icon properties were now set to
C:\MSACCESS.EXE C:\Apps\DB2.MDB /wrkgrp C:\Apps\DB2.MDW

It now created the DB2.LDB. I closed the dabasebase and deleted DB2.MDW
and set the desktop icon properties back to the original line of
C:\MSACCESS.EXE C:\Apps\DB1.MDB /wrkgrp C:\Apps\DB1.MDW

Now, when I open DB2, I have 2 ldbs; DB1.LDB and DB2.LDB.

Is that expected?

I originally thought LDBs were created based on the name of the
database, not the MDW file. Now I'm really confused.

I've compacted the database but I still get 2 ldbs.

Re: Two ldbs for one mdb?

am 12.10.2007 23:53:16 von Arno R

"Salad" schreef in bericht =
news:13gviuvti5rir09@corp.supernews.com...
?
>=20
> I originally thought LDBs were created based on the name of the=20
> database, not the MDW file. Now I'm really confused.

Access creates ldb's for the app AND for the workgroupfile.
Both are Access databases and both use lockingfiles.

I would suggest to try to avoid using the same name for the mdw as for =
the app...
Maybe Access can indeed handle this situation, but I hate it when Access =
is doing 'weird' things.

Arno R