Access works in 365 but not in 2010 version
I've completed an Access app using Access365 on Windows10...this interface will be used by people also on Windows10, but using MS AccessRuntime2010. All of my testing works fine on my machine. I even copied & the file and renamed the ext from ACCDB to ACCDR to simulate the Runtime environment...again, all is well on my machine. However, on the users' machines they are getting incorrect data & error messages.
I know you'll want to know the exact errors & I will post those tomorrow after retesting. The errors do not stop the users from utilizing the application, but what concerns me is that they are getting wrong information. I have code that calculates the distance between two zip codes by using the latitude & longitude of both. When calculating the distance between a zip in NY & one in MN i get over 1,000 miles (the correct value), but when the user is running the app, the result shows as only 8 miles (clearly incorrect). We walked through the exact steps on both PCs to make sure we didn't do anything differently, but we get different results even though we use the same inputs.
Before I start supplying more specifics as far as code & screenshots of errors, I was wondering if there is anything inherent in the difference between Office365 & Office2010 that could lead to such problems. Could there be something missing from the reference libraries that could be problematic? Can MS AccessRuntime even add more references? i'm guessing not.
I suspect i may need to downgrade my PC to 2010 in order to get this resolved, but any suggestions/advice short of this would be appreciated.
I know you'll want to know the exact errors & I will post those tomorrow after retesting. The errors do not stop the users from utilizing the application, but what concerns me is that they are getting wrong information. I have code that calculates the distance between two zip codes by using the latitude & longitude of both. When calculating the distance between a zip in NY & one in MN i get over 1,000 miles (the correct value), but when the user is running the app, the result shows as only 8 miles (clearly incorrect). We walked through the exact steps on both PCs to make sure we didn't do anything differently, but we get different results even though we use the same inputs.
Before I start supplying more specifics as far as code & screenshots of errors, I was wondering if there is anything inherent in the difference between Office365 & Office2010 that could lead to such problems. Could there be something missing from the reference libraries that could be problematic? Can MS AccessRuntime even add more references? i'm guessing not.
I suspect i may need to downgrade my PC to 2010 in order to get this resolved, but any suggestions/advice short of this would be appreciated.
Without the exact error messages, it's hard to guess what might be the problem although the obvious guess is references. Either the library you are using to do the calculation is missing or a different version.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
References will "auto upgrade" to whatever the user has, but they will not downgrade and that is most likely your problem.
The other gotcha is 32 vs 64 bit. One can't run the other (office install, not version of Windows) and you can't mix and match. You can't have Access 32 bit and Word 64 bit.
Jim.