(re-posting, as my original reply hasn't appeared)
MJ said:
Dirk,
We are using Access 2003 and the file format is Access 2002-2003 file
format.
It does happen to be a split database, with all the programming and forms
in
the front end and the data tables in the backend.
This database has been in use for over 2 years and I do not know of any
other time where we have run into thie issue. I am recommending that they
take care of it at the user level for now. However, I also know that in
the
future I may well have to rebuild/create a "new" databases to take its
place
and I would like to be able to get past this issue before it becomes an
issue
again.
I think I would try these options to try to figure out what's wrong:
1) Build a new copy of the table, load it from the original, bind the forms
to the new copy, and see if the problem persists.
2) Build a new copy of the table, *don't* load it from the original, bind
the forms to the new copy, and see if the problem persists.
3) Save and then recreate the form(s) to/from text, using the hidden
Application.SaveAsText and Application.LoadFromText methods. That ought to
remove any corruption in the forms. See if the problem persists.
4. Build brand new forms from scratch and see if the problem exists in them.
Start with a very simple form, and if that works, add to it until it matches
the original.
You're welcome, although so far it seems the only help I can give is the
reassurance that it's not supposed to be this way.