Command buttons won't fire using 64-bit Access 2013

[davef62]

We have an old .mdb database on our internal network used to collect defect information. This has been working fine at all computers through our plant. Our IT department regularly replaces old computers with new ones, the new ones have Access 2013. One of these new computers has the 32-bit version of Access, this database works fine on that machine. The other are the 64-bit version, when I open the database with this version the command buttons on the main switchboard will display but the events associated with them will not fire, nothing happens. I did convert a copy of the database to .accdb and opened it with the 64-bit Access 2013 but the command buttons still did not work. Any suggestions?

[Minty]

Did not work isn't telling us a lot.
Any error codes ? if it stops which line of the code does it stop on and what's the rest of the code?

[davef62]

I get no error codes, does not show any line of code at all, I just click the button, which is supposed to open a form, and nothing happens. This button works on all other machines other than the ones running 64-bit Access 2013.

[Gicu]

Open any module to get into the VBA editor and try to compile the project. You will probably get compile errors due to 32 bit API declarations missing ptrsafe attribute. The easiest fix is to ask your IT to install Office 2013 32 bit instead of 64 bit (the fact that the newer operating system is 64 bit is irrelevant).

Cheers,

Vlad

[davef62]

Thanks Vlad. I did compile the project with no problems, there are no declarations in this project. The only module in the project is one that sends a notification e-mail to a specified group if the user wishes to do so, this has been working fine. The problem occurs at the main switchboard when the database is first opened. The command buttons are not grayed out so they are enabled, just nothing happens when they are clicked on the 64-bit Access machines. I have talked with IT and they will not be installing 32-bit access on any machines.

[Gicu]

Have you set the trusted location on the new machine?

[isladogs]

Presumably the old machines had an earlier 32-bit version of Access (before 2013)
Check whether there are any VBA references marked MISSING on the 64-bit Access 2013 machine. If so, browse to the reference location to fix these
Also if you have any ActiveX controls, or the old calendar control, these may not work in 64-bit Access. If so, you will need to modify code.

There are NO advantages in using 64-bit Access. Personally I would put pressure on the IT department to change back to 32-bit Access