Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / September 2007

Tip: Looking for answers? Try searching our database.

.ldb issues "spreading" to other Access DBs on different servers

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Pamela - 29 Sep 2005 19:40 GMT
This is kind of a repeat posting, so I apologize in advance.  I have read the
numerous posts on .ldb files on servers, but I am in a situation where I do
not have administrative rights to the company's servers.  This situation is
becoming even more complexing since 3 days ago.  Any ideas are welcomed.

Here is the situation:

Access 2002  Databases are housed on servers (2 different servers involved).

The users (including myself) are starting to experience problems with these
files we never had before.  We all run XP on our desktops.

What happens is when I ask all users to get out of the database, there seems
to be a phantom user.  I have examined a function to show all users, & it
will show a user logged on even after she is off (at her desktop).  There is
nothing there under task manager to indicate access is running.

If I myself open an .mdb file on the shared drive, then close out of Access,
I can no longer re-open Access.  It's as though it only allows users to open
it one time.  This is happening to other users too, in applications (Access)
they have never had problems with before.

The only fix seems to be to restart, or to open Access locally (on the
desktop), then go to file>open & open the .mdb file that way.  The company's
desktop support seems stumped too & have referred the case to the server team.

Since this started happening ~3-4 days ago, could the problem be with recent
server updates?   They are currently checking permissions at the directory
level (after I had directed them to a posting here).

I was hoping there might be something else causing this somebody might be
aware of.  My problem not being able to get into design mode (previously
posted) is now obviously related to this problem.  When everyone is logged
out, the ldb file remains.  Only way to get rid of it is to have the user who
still shows as logged in (according to the ShowUsers routine) reboot.  Only
then does the ldb file go away...but even then, once I am able to open the
mdb file, if I close out, I am again unable to open the file on the server!

These were previously trouble-free applications.
Immanuel Sibero - 10 Oct 2005 16:35 GMT
Hi Pamela,

There is probably a reason to believe that the server updates may have
something to do with it. A lot of .ldb related problems are traceable to
user rights and privileges issues. You didnt mention what kind of servers.
Windows 2000? Windows 2003?

I'm also getting the impression that you're not splitting your access
application. True? If so, you should split them to Front End and Back End.

HTH,
Immanuel Sibero

> This is kind of a repeat posting, so I apologize in advance.  I have read the
> numerous posts on .ldb files on servers, but I am in a situation where I do
[quoted text clipped - 35 lines]
>
> These were previously trouble-free applications.
Pamela - 24 Oct 2005 16:10 GMT
Hi.  Sorry for the delayed response.  The whole problem stemmed from the use
of conditional formatting in subforms (Access 2002).  I found the fix in this
forum, & am very grateful.

The problem appeared to be "spreading" because I discovered that when this
particular database was opened by the user, when they closed out they could
no longer open another Access database, all because the initial session
wasn't being released from memory (Task Manager was showing the Access.exe
process as still running).

I removed the conditional formatting from the subform, & it now releases from
memory - & the associated ldb file deletes like it should.  :)  

I will be splitting the database as soon as I am completed finished with
their requests.  

Thanks!

I don't know what kind of servers these are on, I have been trying for a few
days to get that answer (large corp. for you)...I believe 2003 though...

>Hi Pamela,
>
[quoted text clipped - 14 lines]
>>
>> These were previously trouble-free applications.
Elite IT - 07 Sep 2007 21:53 GMT
Is there an affiliate program for Microsoft for businesses to join?

Signature

Nishan Kumaraperu
Elite IT Appleton WI
http://www.eliteitpc.com

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.