MS Run-Time Error when accessing Access database

I have an access database and when I try to access it using either 32BIT or 64BIT run-time I receive the following error message. The database was created in MS Access 2013 and is being accessed using the 2013 run-time program. I am able to access it on the full version of MS Access. Any ideas on how to resolve this issue?

See attached document and error information below.

"This error occurs when an event has failed to run because the location of the logic for the event cannot be evaluated. For example, if the OnOpen property of a form is set to =[Field], this error occurs because a macro or event name is expected to run when the event occurs."
Access-Runtime-Error.docx
csciarroAsked:
Who is Participating?
 
PatHartmanCommented:
We are not talking about the bitness of the machine.  We are talking about the bitness of the MS Office product that is installed.  Just because your computer has a 64-bit processor doesn't mean that the software has to be 64-bit although the Operating system will always match the hardware.  What is the bit version of Office on the development machine? What is bit version of Office on the machine where you want to run the application?  What is the bit-version of the Access runtime on the machine where you want to run the application?  Can you rename the database from my.accdb to my.accdr and run it successfully on the development machine?

PS - you will have nothing but trouble with Access if you have to support both 32 and 64-bit installations of Office.  Standardize on one, preferably the 32-bit version if possible.  If you must support both, you are probably better off developing in the 32-bit version.  You just need to be careful when you use API code because you will need to use conditional compilation.  Even if you develop on 32-bit Access, you MUST have a full version of 64-bit Access on a DIFFERENT computer or in a VM that you can use to create the .accde for the 64-bit Office machines.
0
 
PatHartmanCommented:
Only one bit-wise version of Office applications can be installed on a single computer.  If you have 32-bit Office, you MUST use 32-bit Access or 32-bit Access runtime.

If you create the .accde/.accdr with 32-bit Access you MUST use 32-bit Access or Access runtime to run it.  Same for 64-bit.  You have to run the app with the same bit-wise version you used to create it.

The .accdb is more flexible.  As long as you are not using any Windows API's, your Access .accdb files will work in either version.  If you have API code, and you must support multiple bit-wise versions, you MUST use conditional compilation.

Bottom line - If you don't have to install the 64-bit version of Office don't do it.  Even Microsoft recommends sticking with the 32-bit version.  There is nothing to gain by using the 64-bit version except the ability to create humongous spreadsheets and INMNSHO, that isn't a benefit.  If you use addins, you loose all your addins unless the vendor has also created a 64-bit version.
0
 
csciarroAuthor Commented:
Ok. When I try to access it on a 32 or 65BIT machine with the correct runtime bit version I receive the same error message. any thoughts on how I can correct this without using the full version of access?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.