2003 not saving VBA coding

[manning_news]

Has anyone had a problem with Access 2003 not saving their coding?
I've been using 2003 for a couple of months now and just this week
noticed that some coding I'd done for a database was not there anymore.
I reentered it and didn't have any problems for a couple of days.
Today I entered some coding, saved it, opened another database, and
when I opened my original database again, the coding I had entered was
missing.

Access 2000 always warned me if I tried to exit a form or any database
changes w/o saving first. 2003 warns me as well so I'm not sure where
the problem is.

I noticed that this database was in a 2000 format so I converted it to
2003. (I just noticed that if I create a new database in 2003, it
defaults to a 2000 format.)

I've researched this newsgroup and the knowledge base and can't find
any postings or articles on this.

Thanks for any help or advice.

[Bruce Rusk]

I think something like this has happened to me under certain conditions: it
was code behind a form that had some code running on the Close event;
somehow the code prevented it from asking me about saving the design
changes. It may also be possible if you have multiple instances of something
(e.g. a subform) open.
<ma**********@hotmail.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...

Has anyone had a problem with Access 2003 not saving their coding?
I've been using 2003 for a couple of months now and just this week
noticed that some coding I'd done for a database was not there anymore.
I reentered it and didn't have any problems for a couple of days.
Today I entered some coding, saved it, opened another database, and
when I opened my original database again, the coding I had entered was
missing.

Access 2000 always warned me if I tried to exit a form or any database
changes w/o saving first. 2003 warns me as well so I'm not sure where
the problem is.

I noticed that this database was in a 2000 format so I converted it to
2003. (I just noticed that if I create a new database in 2003, it
defaults to a 2000 format.)

I've researched this newsgroup and the knowledge base and can't find
any postings or articles on this.

Thanks for any help or advice.

[manning_news]

Hey thanks for your reply. I don't think this was my situation but
I'll keep it in mind. I noticed that there is a SP2 upgrade to Office
2003 that mentions enhancements to Access. I'll download the SP then
keep an eye on things.
Bruce Rusk wrote:

I think something like this has happened to me under certain conditions: it
was code behind a form that had some code running on the Close event;
somehow the code prevented it from asking me about saving the design
changes. It may also be possible if you have multiple instances of something
(e.g. a subform) open.
<ma**********@hotmail.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...

Has anyone had a problem with Access 2003 not saving their coding?
I've been using 2003 for a couple of months now and just this week
noticed that some coding I'd done for a database was not there anymore.
I reentered it and didn't have any problems for a couple of days.
Today I entered some coding, saved it, opened another database, and
when I opened my original database again, the coding I had entered was
missing.

Access 2000 always warned me if I tried to exit a form or any database
changes w/o saving first. 2003 warns me as well so I'm not sure where
the problem is.

I noticed that this database was in a 2000 format so I converted it to
2003. (I just noticed that if I create a new database in 2003, it
defaults to a 2000 format.)

I've researched this newsgroup and the knowledge base and can't find
any postings or articles on this.

Thanks for any help or advice.