John, this is almost certainly a kind of corruption of the database, which
is not uncommon during development when objects are constantly being
modified.
Firstly, make sure you have the latest service pack. Does Help | About
indicate SP-2? If not, go to support.micorosft.com, and download this pack.
Locate msjet40.dll (usually in windows\system32), right-click and check the
Version. It should be 4.0.7xxx. If it's not a 7, download the Jet 4 SP7
update.
Next, open a code window. From the Tools menu, choose References. Deselect
any references you don't need. Then check that the application compiles
(Compile on Debug menu). If you are unsure which references you need, see:
http://allenbrowne.com/ser-38.html
If corruption persists, it issue may be related to Access' attempt to keep
track of changes to the names of fields. To avoid this:
1. Create a new (blank) database.
2. Immediately turn of the Name Autocorrect options (Tools | Options |
General).
3. Import all the objects from the old database (File | Get External |
Import).
4. Set your references again, and compile.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
"John" <so*********@hotmail.com> wrote in message
news:90**************************@posting.google.c om...
(access 2002)
Anyone have any suggestions as to what may be causing access to not
save form changes after I "tell" it to, exit database, then re-open
later to discover the changes had not been saved (or somehow
reverted). BUT, new form module code is saved.
Example: created txtTitle control on form. Create AfterUpdate event
code for txtTitle. Save form. Close database. Later...Open database,
open form, txtTitle not there but its event code is.
I also keep getting an error about "communicating with ole server" on
form's OnCurrent, etc. Copying the form and re-pasting seems to fix
this type of error. (I always compact the db)
Any thoughts?
