C
Chris
The Background:
12 computers on our network using access 97.
Have a UNIX based server (NAS) that holds our Access files.
Have time-clock system that spits out .BTR files
We import BTR's into Access 2.0
We view reports in Access 97 that reference the Access 2.0 data (originally
from the time-clock generated .BTR files)
The Problem:
Once in a while after working in the database (in Access 97) the Access 2.0
record locking file gets stuck and no one can get into that table
(obviously). It's always the Access 2.0 locking file. Sometimes I'm able to
delete the file and everything is fine, sometimes I need to reset the
server. This is happening about every other day. I took a look at the
locking file and it's different computers (at different times) locking and
not letting go after they are through with Access. What could possibly be
the problem. It always worked fine for years. Is it the server, Access, or
our workstations? Please help.
The Alibi:
I am just a graphic designer. I did not design our company's database system
(the boss did). But because I know how to turn on a printer I guess I have
just become our Network Administrator (LOL). Which would not be a bad job if
I knew what the hell I was doing. Translation - please try to go easy on me.
Thanks for all your help!!!
-Chris
12 computers on our network using access 97.
Have a UNIX based server (NAS) that holds our Access files.
Have time-clock system that spits out .BTR files
We import BTR's into Access 2.0
We view reports in Access 97 that reference the Access 2.0 data (originally
from the time-clock generated .BTR files)
The Problem:
Once in a while after working in the database (in Access 97) the Access 2.0
record locking file gets stuck and no one can get into that table
(obviously). It's always the Access 2.0 locking file. Sometimes I'm able to
delete the file and everything is fine, sometimes I need to reset the
server. This is happening about every other day. I took a look at the
locking file and it's different computers (at different times) locking and
not letting go after they are through with Access. What could possibly be
the problem. It always worked fine for years. Is it the server, Access, or
our workstations? Please help.
The Alibi:
I am just a graphic designer. I did not design our company's database system
(the boss did). But because I know how to turn on a printer I guess I have
just become our Network Administrator (LOL). Which would not be a bad job if
I knew what the hell I was doing. Translation - please try to go easy on me.
Thanks for all your help!!!
-Chris