I am sorry, I forgot to mention earlier, there is one more setting you need to do. Isn't the app just supposed to open just like it does on my development machine? If so, any ideas on what i am doing wrong? Or am i misunderstanding how this is supposed to work? Any help would be appreciated On the status bar at the bottom, there is an Access logo and the words Powered by Microsoft Access. The only options on the file tab are print, privacy options, and exit. When i open the app with a double click on the file, I get a blank page with only the file tab. It does not have Access but I have downloaded the 2010 RunTime and installed it. I open the form and the application seems to work fine and the design views for the objects are not available, as expected. It finally displays the form that i use to control the entire application. I test it on this machine and it comes up in a weird mode - i have to right click and play with options in the nav panel on the left. I use the Save & Publish - Save As functions on the file menu and get an accde file.
#Trust location on access runtime 2010 full version
This will provoce Access to run the file same as you would start it with the /runtime parameter.Īlternatively you can install the Access 2010 runtime to these computers beside the Access 2013 full version and start it using the full qualified path to MSACCESS.EXE of the A2010 version.I am trying to get an accde file to work on a second computer. To prevent users doing stuff they shouldn't do in Access2013 you also may just rename it to ACCDR. ACCDE to fool the users) then it will not be possible to have the app running on A2013. If you can't deliver the ACCDB (which also can be renamed to.
#Trust location on access runtime 2010 code
The reason you get the error probably is that A2013 want's to build the bytecode (compiling the source code) but the ACCDE doesn't have the source code in it. Specific features which are causing the incompatibility.Īs the application has been built in A2010 there can't be any features inside that aren't compatible. Within Access 2013 that wasn't obvious or perhaps removing some There might be a way of creating a runtime 2010 compatible accde from
"Dan Semkiw" schrieb im Newsbeitrag I thought I can't test it as I don't have A2013 installed (and refuse to install any O2013 products with the current licensing limitations). It may be possible to open an A2013 ACCDE that doesn't contain any VBA code in A2010, but I'm not sure. Would be any functionality in it it doesn't know it now would give you a compilation error. If you start the ACCDB A2010 now can "decompile" your application and compile it before running the code. Access 2010 therefore is forced to drop the bytecode (same as you do a /decompile manually) and rebuild it by compiling the canonical code.Īs the ACCDE doesn't contain any canonical code, only bytecode, Access fails doing so and tells you that the database is in a unknown format. (the compilation of the canonical (AKA text) code) may not fit. A2010 doesn't know if the bytecode contains any functionality that A2010 didn't provide. Access 2010 now realizes that a newer version was used. When you edited the ACCDB in A2013 then some flags are set about the version that was used.
0 kommentar(er)
