P
psu2000
I have a coworker who is experiencing problems with a database that
she created. The main table in this database lists client information,
including first name, last name, address, etc. Within the past 1-2
weeks, they've noticed problems where people's information is
incorrect when they pull records back up. For example a record this
morning came up with a man's name being switched from Lawrence to
Elizabeth... In every case, the field now contains the same
information that is in the record before it.. so for example in this
case the record before the one for Lawrence was for a women named
Elizabeth. This has happened in several fields so it doesn't appear
that one particular field is the problem.
I have already asked them to watch for people accidentally using the
CRTL+apostrophe key combo and was told this was not the problem
(although I have not watched any data entry to be sure this is not the
case.) I also know that there are some other things that need to be
done to this database to help prevent user input errors (specifically
creating a data entry form so staff are not able to delete/change
current records.) This will all be done after the program ends in
September.
However, for now, the problem of record corruption continues.. Are
they any thoughts to what might be occurring here?? My thoughts keep
going back to user input errors but even then I don't know what they
are doing to cause this.
Thanks.
she created. The main table in this database lists client information,
including first name, last name, address, etc. Within the past 1-2
weeks, they've noticed problems where people's information is
incorrect when they pull records back up. For example a record this
morning came up with a man's name being switched from Lawrence to
Elizabeth... In every case, the field now contains the same
information that is in the record before it.. so for example in this
case the record before the one for Lawrence was for a women named
Elizabeth. This has happened in several fields so it doesn't appear
that one particular field is the problem.
I have already asked them to watch for people accidentally using the
CRTL+apostrophe key combo and was told this was not the problem
(although I have not watched any data entry to be sure this is not the
case.) I also know that there are some other things that need to be
done to this database to help prevent user input errors (specifically
creating a data entry form so staff are not able to delete/change
current records.) This will all be done after the program ends in
September.
However, for now, the problem of record corruption continues.. Are
they any thoughts to what might be occurring here?? My thoughts keep
going back to user input errors but even then I don't know what they
are doing to cause this.
Thanks.