G
Guest
Hello all- this is the first time I've ever asked a tech question on this
forum so bear with me as i try to explain the issue...
I work with a large MSAccess database (XP), housing hundreds of records,
that is shared with several users in my office. To save time in data entry,
I open several records at a time and complete the redundant information
(names, dates, etc.) before entering questionairre answers. I have NEVER had
a problem with this... except for today.
I had 4 records open and had completed all the redunant info and started
entering the new info. When I finished with one record and tabbed to the
next, I found that all of the cells, the ones I had completed and the blank
ones, were filled with "#Deleted." This occurred for only 2 of the 4 records
I was working with. I asked everyone else on my team if they had deleted
any files but no one claimed to have done so.
When I searched google for the error, one answer came up for Access 2000 -
apparently there was a bug that could cause this problem... Can anyone tell
me if I'm dealing with a bug in Access 2002? Or is it something else? I
really appreciate your help.
Regards,
Jennifer
forum so bear with me as i try to explain the issue...
I work with a large MSAccess database (XP), housing hundreds of records,
that is shared with several users in my office. To save time in data entry,
I open several records at a time and complete the redundant information
(names, dates, etc.) before entering questionairre answers. I have NEVER had
a problem with this... except for today.
I had 4 records open and had completed all the redunant info and started
entering the new info. When I finished with one record and tabbed to the
next, I found that all of the cells, the ones I had completed and the blank
ones, were filled with "#Deleted." This occurred for only 2 of the 4 records
I was working with. I asked everyone else on my team if they had deleted
any files but no one claimed to have done so.
When I searched google for the error, one answer came up for Access 2000 -
apparently there was a bug that could cause this problem... Can anyone tell
me if I'm dealing with a bug in Access 2002? Or is it something else? I
really appreciate your help.
Regards,
Jennifer