G
Guest
Hi,
I have had a small Access database in use for about 2 years now. It has
been working well, with the exception that we get occasional errors and
sometimes corruption requiring a compact/repair.
The db is stored on a network drive. We tried it both with the front end
stored on the client pc's, and also with the users sharing the same front
end. Our IT group, of course, knows Access was designed to have the front
end installed on client. However, we get the same errors either way.
There are about 5 users total at any one time. A total fo 10 users have
access to the db.
In researching the errors, they seem to have to do with connectivity, and
broken connections. Some seem to have to do with corrupted workspace
occupied by the db. Below is a list of errors we have received on more than
one occasion.
The errors are experienced by all users who are logged in at the time,
whether or not the front end is shared, or whether it's installed on the
clients.
I'd like to have some suggestions as to whether these are indeed
connectivity issues, or any other advice anyone may have. Thanks!
Errors:
Disk or network error.
#NAME (appears in all fields).
#DELETE (appears in all or some fields).
Auto ID number becomes scientific and exponential in value (e.g. next id #
should be 2345 but instead is something line 18989899334).
Chinese language characters appear in some fields with "Record Changed by
Another User" message poppping up.
"The Microsoft jet database engine could not find the object "Scripts".
Make sure the object exists and that you spell the name and the pathname
correctly."
"The changes you requested to the table were not successful because they
would create duplicate values in the index, primary key, or relationship.
Change the data in the field or fields that contain the duplicate data,
remove the index, or redefine the index to permit duplicate entries and try
again."
"There was an error executing the command" (happened while trying to click
on a switchboard entry).
"The macro (or its macro group) doesn't exist, or the macro is new but
hasn't been saved. Note that when you enter the macro group name, macro
name, syntax in an argument, you must specify the name the macro's macro
group was last saved under."
Many thanks,
Rosemary
I have had a small Access database in use for about 2 years now. It has
been working well, with the exception that we get occasional errors and
sometimes corruption requiring a compact/repair.
The db is stored on a network drive. We tried it both with the front end
stored on the client pc's, and also with the users sharing the same front
end. Our IT group, of course, knows Access was designed to have the front
end installed on client. However, we get the same errors either way.
There are about 5 users total at any one time. A total fo 10 users have
access to the db.
In researching the errors, they seem to have to do with connectivity, and
broken connections. Some seem to have to do with corrupted workspace
occupied by the db. Below is a list of errors we have received on more than
one occasion.
The errors are experienced by all users who are logged in at the time,
whether or not the front end is shared, or whether it's installed on the
clients.
I'd like to have some suggestions as to whether these are indeed
connectivity issues, or any other advice anyone may have. Thanks!
Errors:
Disk or network error.
#NAME (appears in all fields).
#DELETE (appears in all or some fields).
Auto ID number becomes scientific and exponential in value (e.g. next id #
should be 2345 but instead is something line 18989899334).
Chinese language characters appear in some fields with "Record Changed by
Another User" message poppping up.
"The Microsoft jet database engine could not find the object "Scripts".
Make sure the object exists and that you spell the name and the pathname
correctly."
"The changes you requested to the table were not successful because they
would create duplicate values in the index, primary key, or relationship.
Change the data in the field or fields that contain the duplicate data,
remove the index, or redefine the index to permit duplicate entries and try
again."
"There was an error executing the command" (happened while trying to click
on a switchboard entry).
"The macro (or its macro group) doesn't exist, or the macro is new but
hasn't been saved. Note that when you enter the macro group name, macro
name, syntax in an argument, you must specify the name the macro's macro
group was last saved under."
Many thanks,
Rosemary