We help IT Professionals succeed at work.

MS access Macro issue(AutoExec

ncomper
ncomper used Ask the Experts™
on
Hi All,
         I have a client with a MS Access DB created in Access 2000/3. I have found when running the DB in Access 2007/10 that i receive the following error.

Macro Error
Running the Db within Access 2003 continues to work. I beleive that there may have been a change to the AutoExec between the versions that is causing the issue.

Is there any way to upgrade/Recompile this to be compatable with the new 2010 version of access?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Chris BRetired
Commented:
It is not the macro, it is a missing reference. Open a code window and click Tools - References, then look for something marked missing. Substitute a current routine for this or see if you can add it, but the issue will be here.

Chris B
Top Expert 2016
Commented:
- did you place your db in a  trusted location before running in A2007/A2010 ?

- open your VBA window,
Tools > references

- look for references with MISSING prefix, uncheck and locate available library and select

while in the VBA window, do
Debug > Compile
check which line is highlighted, you may have used VBA commands that are no longer supported in A2007/A2010

Author

Commented:
Thanks for the posts please see the below image, i have scrolled down and there are none with MISSING i can see

I am a complete novice when it comes to this so feel free to offer stupid steps :)

VP_View
Top Expert 2016
Commented:
ok.. now do this


while in the VBA window, do
Debug > Compile
check which line is highlighted, you may have used VBA commands that are no longer supported in A2007/A2010

Author

Commented:
We seems to be getting there now......

it seems that a 32 bit system can open the DB now but it wants the below for a 64bit

32-64
i can confirm the comdlg32.dll is in my system32 folder
You are using a 64-bit version of Office.

The message is telling you you have to change your code in order to run the app in 64-bit office and is correct.

Unless you have a well thought IT plan for using 64-bit Office this is probably only the first of several problems you are going to meet.
Top Expert 2016

Commented:
yep..as it is stated in the error message..

Author

Commented:
Excelent....

32bit office it is then as this is only a single user item, if they want to roll it out i will have them plan out a re-development/Code re-write.

Many thanks,