BarryDev84
New member
- Local time
- Today, 06:22
- Joined
- Aug 4, 2008
- Messages
- 2

We have a shared network drive that is running Windows 2003 SP2 where the database front & back ends are located.
Any number of concurrent users from Co1 can successfully log into the database and the .ldb file looks normal.
However, the only way a user from Co2 can get in, is if they are the first user, i.e. they create the ldb file. This .ldb file appears to contain garbage - crucifixes, squares etc.
However a Co1 user can still get in, and the .ldb file now looks to contain the correct information for both users.
If the Co2 users logs out and attempts to get back in, they can no longer do so.
My guess is that they can no longer read the now "correct" .ldb file.
Multiple users from Co2 are not able to access the database even if no users for Co1 are logged in.
Both groups of users have identical permissions on the drive and the individual files and folders within it.
Both groups of users are running Windows XP SP2 on their desktops.
Co1 are using Office 2003 whereas Co2 are using Office 2000.
In both cases the Access 2003 runtime components have been installed on the individual PC's.
I have experimented with some test databases and got the same results, so I dont think that the problem is with the database itself.
The apparent corruption with the .ldb file may be a red herring, but I am getting desperate !
Has anybody please got any idea what I need to do to resolve this ?