Database reporting changesto forms when this is untrue

[Guest]

Hi all,

I am an IT support techie for a company using a Access Database to hold
information for document control. The problem we are having is that the
database was recently copied for use by another part of the company and since
then our Engineering Admin has been receiving some odd errors on an
intermitant basis. Sometime upon closing the database a message will pop up
saying that the "main screen" (our central form) has been changed since the
last time you opened it either by another user or because another instance of
it was opened on this machine.

Now we are sure that there is no link between the copy that was taken of the
database and the original version in use with the admin however we are at a
loss as to how 1 user with only 1 copy of the database running could produce
such an error as they do not have access to the form design screen. The
database is stored on our central Win2k3 server and accessed through a
shortcut on the user's desktop but i'm not sure if this would make the
difference? Any thoughts?

Many Thanks

 

[Rick Brandt]

Hi all,

I am an IT support techie for a company using a Access Database to
hold information for document control. The problem we are having is
that the database was recently copied for use by another part of the
company and since then our Engineering Admin has been receiving some
odd errors on an intermitant basis. Sometime upon closing the
database a message will pop up saying that the "main screen" (our
central form) has been changed since the last time you opened it
either by another user or because another instance of it was opened
on this machine.

Now we are sure that there is no link between the copy that was taken
of the database and the original version in use with the admin
however we are at a loss as to how 1 user with only 1 copy of the
database running could produce such an error as they do not have
access to the form design screen. The database is stored on our
central Win2k3 server and accessed through a shortcut on the user's
desktop but i'm not sure if this would make the difference? Any
thoughts?

Many Thanks

In this case "another user" really means "another process". Having two forms
editing the same record or editing a record in a form while simultaneously
running an update query against the table affecting the same record are common
ways to trigger that error.

Without knowing more about your form and what the user is doing it would be
difficult to pinpoint any further.

 

[Arvin Meyer [MVP]]

The
database is stored on our central Win2k3 server and accessed through a
shortcut on the user's desktop but i'm not sure if this would make the
difference? Any thoughts?

Actually, that could be the reason. Databases designed for multiple use
should be split with only the data tables on the server linked to individual
copies of the application (forms, etc.) on each workstation.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access