Database gets Macro errors after being opened and changed in Access 2007

[ekharonne]

Hello Anyone,

I have a somewhat intresting issue. My organization is still mostly using Office 2003. Recently, I have been upgraded to 2007. I have been coding and designing an access database application. In access 2007, I have saved the format in 2003 mdb, however, when I open the database in 2003 my autoexec macro will not run. I recieve the "halt" error. Can anyone help me understand what access 2007 changed in my database that would cause my autoexec macro not to run in 2003? I have been searching the internet all morning and yesterday for a solution.

Thank you

 

[gemma-the-husky]

I would run the steps in the macro one at a time manually, and see what happens. or convert the macro to code, and then you can examine the code. It's probably something quite trivial.

 

[ekharonne]

Hey Huskey,

I stepped through the macro in Access 2007; no issues. I stepped through the macro in Access 2003 and receive the stop error on a built-in function called setcurrentyear(). The function is in a vba module but called from the runcode macro feature. I am very confused why I would recieve a halt error on this code in access 2003 but not in access 2007. It worked fine in 2003 before I opened and saved the database in 2007.

What are your thoughts?

 

[ekharonne]

Thank You Husky,

Your recommendation to step through the macro step by step worked. I found out that the function was commented out in my code. It is weird that 2007 did not fuss about this but 2003 made a big stink about it. Anyway, thanks for the troubleshooting advice. I would have never thought to step through the macro. I thought is was some weird 2007 security issue with macros.

Kharonne