NO VBA Code Will Execute

[cjl8on]

I have a database I created in Access 2016 32-bit. A user was recently upgraded to Access 2019 64-bit. The front end is an accdb file and she copied it to the exact same location that she ran the 2016 file from. All security controls are handled via enterprise policy, so she has all the same policies that I do. However, NO VBA code will execute across the entire front end set of forms and reports. Not even a simple test button I just inserted that does nothing more put up a message box.



All the buttons that were created with built in macros or the Command Button Wizard work fine, but nothing with VBA works - not even opening the form to the latest record on load.

I've read some articles about using prtsafe and longptr to convert 32-bit to 64-bit, but I don't have any "Declare" or "Long" statements anywhere so I don't know if that applies or what else I might need to do? Does anyone have any thoughts?

[Welshgasman]

How did she get the new file?
If downloaded you need to unblock it in file properties.

PtrSafe etc is only for any APIs. It would still run, but error most likely.

You should not be supplying a accdb, but an accde at least.

https://www.google.com/search?q=unbl...hrome&ie=UTF-8

[cjl8on]

She did not get a new file. She used the same Access file she already had on her computer, probably on her desktop or somewhere local, the same file that was working fine before her MS Office upgrade. She can still open the file and see all the data and many of the buttons still work, just not anything with VBA.

[cjl8on]

I've done some more googling and I am thinking it might be Active X Settings. The behavior is similar to when that Security Warning comes up with the "Enable Content" button. If only had access to adjust the Trust Center settings. Stupid enterprise policies!!

[CJ_London]

A accdb file that has been opened and run with 32bit access will not subsequently execute properly when opened in 64bit and visa versa. Not sure of the exact reason why but something to do with settings being created. I had the issue when playing around with the new northwind

suggest provide a new front end or perhaps try decompile/recompile in 64bit then compact/repair.

another option to try, on the users machine create a new empty db then import all the objects from the old db - do it in order tables, then queries, the modules/macros and finally forms then reports