Access Be file

  • Thread starter Thread starter Sharon
  • Start date Start date
S

Sharon

I have a be file for our database. When one computer opens their own front
end, it puts a ldb on the back end, which locks the other front end??? The
only thing that that computer has that is different is the other computers
are running MS Office 2000 and the problem one is the latest version. Would
that create a problem?
 
Do the users have the same permissions on the folder where the database
exists? Even if they're not updating the database, they need at least
Create, Read and Write to the folder. I've heard of problems, too, where
they may have Create permission, so that they can create the ldb file if
they're the first user in, but they don't have Write permission to the ldb
file if someone else created it.
 
No, that is not the problem.
The reason you are seing a be ldb open is because when you open the fe that
links to the be, it creates an ldb file for the fe and one for the be.

The issue may have to do with versions or with how you have your locking
rules set in the newer version. Is it 2007 or 2003? Note that the newer
version has to be set to use the version your be is in.
 
What kind of problems are you seeing? Which version of Access is the CompFrE
made with? Which version is the CompBE made with? Have you tried Save -
"save the database in another format" with the Access2007 computer?
 
Whenever an mdb file is accessed, either the frontend or the backend, it will
open an ldb file. Are all of the computers opening a copy of the frontend on
THEIR computer and not a shared frontend in a network location? That is what
needs to happen. Plus each user needs to have read/write/delete rights to
the backend network location.

--
Bob Larson
Access World Forums Super Moderator
Utter Access VIP
Tutorials at http://www.btabdevelopment.com
If my post was helpful to you, please rate the post.
__________________________________
 
The problem is not with the ldb files. When you open a front end it creates
an ldb file for the front end and the links to the back end cause the back
end file to open thus creating an ldb file for the back end. This is the
normal situation.

What version of Access is the back end database? What version is running on
the computer that has the problem? It may be there is an incompatibility
problem between the versions.
 
Each user has their own front end copy. When the one use opens any copy
(which all copies are on the server) it opens an Idb and also one on the BE
database? We have been using this for 2 years with out this problem. That's
what leads me to believe it has to do with the software update.
 
You sure your network people didn't make changes to the permissions on the
server folder where the back-end resides at about the same time the upgrade
took place?

The behaviour Bob described has been true for every version of Access.
 
Are the computers that you ran the update on the computers that are having
the problem? Are there other computers that you did not run the update on
and are they having the problem? What update did you have run? Was it an
Office update or a Windows Upgate?
 
Back
Top