Re: Do Transactions guard against corruption?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

JString <JString@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Yes, the company that I work for is having a few problems with the back end
being placed in a locked state. After restoring it, I've noticed that there
are a few people who's usernames have not been removed from the user table
which makes me think that they're just powering off their workstations
instead of correctly shutting down, and I've read that that is known to place
databases into suspect states. We use Access 2003 though so if that is
really the problem then is it possible that the issue was never really fixed?

But just viewing the contents of the LDB file can be misleading.

Opening the .ldb file using notepad will show you both who's currently
in the database and some of the workstations which were in the
database. When a person exits Access their workstation name and
Access login id, Admin unless you are using Access security, are left
in a "slot" or record in the ldb file. This slot or record may get
overwritten the next time someone enters the MDB depending on what
slot or record is available previous to it in the ldb file.

Determining the workstation which caused the Microsoft Access MDB
corruption
http://www.granite.ab.ca/access/corruption/workstation.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
.

Relevant Pages

  • Re: security problem with ms-access?
    ... all workstations have the frontend on their ... Microsoft Access will not open this file due to potential security problems. ... "ms-access could not open the file ... ...
    (comp.databases.ms-access)
  • Re: setting up the network path for workstations
    ... and mapping to link the front end of an application, on workstations, to the ... In my opinion using drive letters is fine so long as they are ... same server and share then that will work. ... Tony Toews, Microsoft Access MVP ...
    (microsoft.public.access.setupconfig)
  • Re: Identify PC by ldb
    ... I tried the WindowsUserID code in api0008.htm as described in a different ... currently in the database then you know that that user exited out abnormally ... All I need to know is how to extract the PC name from the ldb file. ... Determining the workstation which caused the Microsoft Access MDB ...
    (microsoft.public.access.modulesdaovba)
  • Re: Identify PC by ldb
    ... table in the backend and then in your startup routine append key information ... record exists in the database from a few days back and you *know* no one is ... All I need to know is how to extract the PC name from the ldb file. ... Determining the workstation which caused the Microsoft Access MDB ...
    (microsoft.public.access.modulesdaovba)
  • Re: Identify PC by ldb
    ... opened an ldb file opens with it. ... All I need to know is how to extract the PC name from the ldb file. ... Opening the .ldb file using notepad will show you both who's currently ... Determining the workstation which caused the Microsoft Access MDB ...
    (microsoft.public.access.modulesdaovba)