Re: My ritual question for each new version of Access since 2000

Well, if you are dumb enough to put two files in the same directory with
the same name, ms-access creates a locking file based on the filename.

Yes, this is the way Access works by default. MDE in the same folder as MDB,
and with the same project name.

But even if you call this dumb, the problem with locking is bigger than
that. It's not to difficult to lock up a file even if you are the only
user in a new instance of Access.

(david)

"Albert D.Kallal" <PleaseNOOOsPAMmkallal@xxxxxxx> wrote in message
news:Rsxfg.219740$WI1.4495@xxxxxxxxxxx
Well, if you are dumb enough to put two files in the same directory with
the same name, ms-access creates a locking file based on the filename.

So, even if you are not using library code, you always had to avoid this
problem.

The solution is to move out the mdb from the directory that created the
mde. Another solution is to name the mdb and the mde file differently.

As I pointed out in my other post, it is not really a big deal. You can't
have multiple users editing the code. However, you can edit the mdb used
to create the mde (if you move it to a different dir, or give it a
different name). Remember, even your workgroup file name has to be
different. I once made the mistake of naming my workgroup file the same
"prefix" name as the mdb. Don't do that!!

The reason is that ms-access also creates a .ldb file for EACH application
it opens (this includes workgroup files, and library files).

So if you have

mydb.mdb
mydb.mde
mydb.mdw

In the above 3 files, they all have the same prefix. Only ONE locking file
can be created called

mydb.ldb

so, tell me Sherlock, to which of the above 3 applications does the ldb
file apply to? You got a real mess here.

So, if the original poster simply adopts a naming convention, or simply
places the mdb file in a different directory then the mde file, then that
person CAN FREELY OPEN and edit the library mdb file.

The stated problem GOES AWAY. It is a trivial matter to avoid the original
posters problem. If you are telling me that the fact of ms-access creating
a ldb file based on the file prefix name is a problem, I have no beef with
that. However, this is not a new problem.

There is few, if any IDE's that allow multiple users into the same code
base at the same time. It is just not done, and the fact of this being
changed from a2000 onward is a moot point if one *slightly* changes their
development practices.

If a person can't adopt the simple and slight changes in their approach to
developing software, then I have to question that persons ability to
develop software.

The suggestions I made in other responses to this post are of a VERY minor
change in coding and approach. This changes will not result in ANY drop,
or loss of productivity in any measurable way that I can think of.

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@xxxxxxx
http://www.members.shaw.ca/AlbertKallal



.

Relevant Pages

  • Re: Converting Access 97 MDE to Access 2003
    ... what is the MDB front-end you are ... The mdb front end is of course the original mdb you had to make the mde. ... ms-access is the in the SAME VERSION as what you are developing under. ... a mde file is created by going tools->database utile. ...
    (microsoft.public.access.conversion)
  • Re: My ritual question for each new version of Access since 2000
    ... ms-access creates a locking file based on the filename. ... The solution is to move out the mdb from the directory that created the mde. ... Another solution is to name the mdb and the mde file differently. ... The reason is that ms-access also creates a .ldb file for EACH application ...
    (comp.databases.ms-access)
  • Re: Lock / Unlock VBA project
    ... "Alex Dybenko" wrote: ... make MDE? ... library MDB - create ne mdb, import forms/modules from your app, which ... have to make MDE of it and add reference to library MDE in order to make MDE ...
    (microsoft.public.access.modulesdaovba)
  • Possible Fix for "Unable to create MDE" Error and "Unexpected Error 40230" in Access 2002
    ... compile it and create an MDE on the local disk. ... With each one I progressively deleted more and more objects in the mdb until ... Dev PC is WinXP SP1. ...
    (microsoft.public.access.conversion)
  • Re: Open main form with an icon without Access
    ... Once the runtime is installed, then you can copy any mde, or mdb file to ... So, make no mistake here, that runtime is a full ms-access install, and the ... So, while the term "stand alone" is often used, it is OFTEN a miss leading ...
    (microsoft.public.access.forms)