M
Mootcat
I am doing some work for a company that has a Windows 2003 R2 server. They
are running access 2003 which has two users that are allowed to update. Then
one of the users converts the database to access 2007 for all other users.
Recently one of the users lost her PC so I had to jury rig another one until
her new one arrives. One problem that she was having is that if she did not
open access before the other women (The one in charge) she could not open it
at all. There are no error messages. If the other woman closes access then
the one with the make shift set up can open the database and work on it and
so can the original user.
If the woman with the makeshift PC opens access first then the other woman
has no problems.
They tell me that this was not the case before the inflicted users PC crashed.
As far as I know nothing was changed at the server level so I think it must
have something to do with group membership or some such.
I am not up on my server side stuff so if anyone can tell me what to look
for I would appreciate it greatly.
are running access 2003 which has two users that are allowed to update. Then
one of the users converts the database to access 2007 for all other users.
Recently one of the users lost her PC so I had to jury rig another one until
her new one arrives. One problem that she was having is that if she did not
open access before the other women (The one in charge) she could not open it
at all. There are no error messages. If the other woman closes access then
the one with the make shift set up can open the database and work on it and
so can the original user.
If the woman with the makeshift PC opens access first then the other woman
has no problems.
They tell me that this was not the case before the inflicted users PC crashed.
As far as I know nothing was changed at the server level so I think it must
have something to do with group membership or some such.
I am not up on my server side stuff so if anyone can tell me what to look
for I would appreciate it greatly.