J
Jane Edgecombe
I have a split database with the front-end being used by
a number of people. There is an intermittent problem
which affects some, but not all, users. I have one form
for entering new records and a second form for updating
existing records. When the user enters updates on the
update form, the new data is not saved. No error
message is returned. Sometimes it can take the user 4 or
5 attempts to get the data to "stick". However, if the
user moves to a colleague's workstation, the update is
carried out without any difficulty. The form is linked
directly to the underlying table, and not to any query.
My first thought was database corruption, but running
Compact & Repair on both front and back ends has not
cured the problem. Neither has installing the Office
Service Packs. I also thought that it might be a record-
locking problem but no message is returned. It is odd
that not all workstations have the problem, and that it
is intermittent. I feel that it might be a network
problem but need to explore all other possibilities as
the network is not my responsibility and I don't want to
pass the buck unless I am certain it is not a problem
with the database itself.
If anyone has any ideas, I would be so very grateful
Thanks in advance.
a number of people. There is an intermittent problem
which affects some, but not all, users. I have one form
for entering new records and a second form for updating
existing records. When the user enters updates on the
update form, the new data is not saved. No error
message is returned. Sometimes it can take the user 4 or
5 attempts to get the data to "stick". However, if the
user moves to a colleague's workstation, the update is
carried out without any difficulty. The form is linked
directly to the underlying table, and not to any query.
My first thought was database corruption, but running
Compact & Repair on both front and back ends has not
cured the problem. Neither has installing the Office
Service Packs. I also thought that it might be a record-
locking problem but no message is returned. It is odd
that not all workstations have the problem, and that it
is intermittent. I feel that it might be a network
problem but need to explore all other possibilities as
the network is not my responsibility and I don't want to
pass the buck unless I am certain it is not a problem
with the database itself.
If anyone has any ideas, I would be so very grateful
Thanks in advance.