problem with saving code

[richardconers]

very strange problem:
I upgraded to windows XP and Access XP simultaneously (I have office
xp professional). When I write VBA code in modules and click save,
often several times, I find frequently that the "saved" code is lost.
The module reverts to a status perhaps 2 or 3 three saves prior to
closing. I've been copying code to Word files before closing Access
to cope with this, but does anyone have any idea of what is going on?

I'm absolutely sure that I'm clicking save before closing the modules
and closing Access (it even presents the dialog box listing the other
unsaved objects to be saved which of course I click OK to).

I need to exorcise the evil spirit in my database.

 

[Allen Browne]

Decompile a copy of the database by entering something like this at the
command prompt while Access is not running. It is all one line, and include
the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

You should also check that you have at least SP2 for Office XP, *and* SP8
for JET 4 installed on your new setup. If not, grab them from the Downloads
section at:
http://support.microsoft.com
Other suggestions on avoiding corruption
http://members.iinet.net.au/~allenbrowne/ser-25.html

 

[Frank Stone]

hi,
i think it is xp itself. i hear alot of users in the
newgroups (excel included) say that wierd thinks are going
on in xp. I have xp on my home pc and have expereced odd
things. I am suggesting that this be reported to microsoft
support directly.
regards
Frank

 

[Kevin K. Sullivan]

You aren't, by any chance, modifying a form's code module while that form is
open in Form View, are you? I believe that this specific situation will
result in loss of code changes (the Save button appears to work properly but
the changes aren't actually saved) but it applies only to Form code. Always
put a form into Design View before modifying code.

Kevin