Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
My organization is in the process of upgrading from Access 2003 to Access 2007. One of the apps I am tasked with upgrading is returning very odd errors while opening and closing forms that have nested forms. Have the events changed between Access 2003 and Access 2007 ? The events seem to be firing in a different order in 2007 then they did in 2003.
I haven’t encountered the situation you described. I can’t find anything which mentions changes to forms event model. Allen Browne has some information about Access 2007 compatibility with older versions:
http://allenbrowne.com/Access2007.html#Compatibility
The only problems I experienced so far with 2003 MDBs in Access 2007 were due to broken references. If you haven’t already done so, double-check yours (Tools-> References) from the VB editor. While there, try Debug -> Compile to verify whether your code will compile without errors in Access 2007.
Tony Toews’ Corrupt Microsoft Access MDBs FAQ could help fix or rule out odd behavior due to corruption:
http://www.granite.ab.ca/access/corruptmdbs.htm
If you’ve done those things, and still have problems with certain forms, it might be useful to create a new blank database and import those forms (and objects they depend on) into the new database.
Sorry to scatter-shot this thing. It might help if you could provide more detail about the nature of the errors you’re getting.