MyApp.AccDE -> MyApp.accDR (I recommend this choice). So if you not sure if you running office x32 or 圆4, and ALSO if you not sure if you running a CTR version of office (or a MSI version) or not, then a quick and simple way to test as runtime is to re-name the extension to end in r. To do this (but do ask and I will follow up as to why this is so important). I simply don’t have the pages of space here as to why you want You THEN re-name that accDE to an accDR for testing as runtime. However, you REALLY (and I mean, really really) want to first try a debug->compile in the VBA editor and THEN create an accDE. What you do is make a copy of the application, and re-name the extension from accDB to accDR. Ok, now that we cleared up the above, there is ALSO a SECOND way to test + run + view your application as runtime. So I suspect when you say “not working”, are you saying the program launches and does not work, or the shortcut does not even run Access? (a REALLY important detail here) You THEN need to determine if you are running a CTR version of office (most if not all 365 versions of office will be CTR).
So you first need to determine if you running office x32 or office 圆4. However, if you using an office 365 version, then you are using what is called CLICK TO Run (CTR)Ĭ:\Program Files (x86)\Microsoft Office\root\Office16\MSACCESS.EXEĬ:\Program Files\Microsoft Office\root\Office16\MSACCCESS.EXE It is possible you are running the 圆4 bit version of office, and thus you would use:Ĭ:\Program Files\Microsoft Office\Office16\MSACCCESS.EXE
The above assumes Access x32, and a non click to run version.
Ok, first your shortcut does not look right.Ĭ:\Program Files (x86)\Microsoft Office\Office16\MSACCESS.EXE
0 kommentar(er)
