We help IT Professionals succeed at work.
Troubleshooting Question

Need help using the Access runtime with Access o365

56 Views
Last Modified: 2020-09-24
I have a MS Access application which I compile into an accde using Access o365.  When I attempt to run the application from my Desktop computer with MS Access o365 installed everything works perfectly....HOWEVER..

When I install the Microsoft Access Runtime 2016 - en-us program, then attempt to run the same application (after rebooting) I get the error:

The expression On Open you entered as the event property setting produced the following error: No Current Record

Can anyone help?  I'm not sure how to tell what part of the code is causing the problem.  When I first log into my application at least 11 forms are open as hidden forms to establish persistent connections to the BE, in addition a log-in screen appears.

My screen never changes... ie.. I have no idea what line of code is causing the problem... I'm also not sure whether I'm using the correct runtime...

This machine is using WIndows  7. I have not tried the runtime on a WIn10 machine.

Any help would be appreciated.  Thanks.




Comment
Watch Question

CERTIFIED EXPERT
Most Valuable Expert 2013

Commented:
Do you have the accdb in a Trusted Location (Based on either Office settings already set on the same PC or added to the Registry?)
https://www.experts-exchange.com/questions/29167538/Access-2016-Runtime-Trusted-Locations-Setting.html
Jim Dettman (EE MVE)President / Owner
CERTIFIED EXPERT
Fellow
Most Valuable Expert 2017

Commented:
<< I'm also not sure whether I'm using the correct runtime... >>

 At a guess, 32 vs 64 bit.   You can't mix bitness from Access 2013 and up.

 The other issue would be references.  If you've used anything (like outlook) and set a reference to it, the target machine must have those programs/references available.

Jim.
Anders Ebro (Microsoft MVP)Microsoft Developer
CERTIFIED EXPERT

Commented:
Why are you installing a runtime if you have 365?


what happens if you don’t compile it?

CERTIFIED EXPERT
Most Valuable Expert 2015
Distinguished Expert 2018

Commented:
I have a MS Access application which I compile into an accde using Access o365.
Then it must run with Access 365.

If you wish also to provide an mde that runs with Access 2016, you must create that mde with Access 2016.

Further, if users may have a mix of 32- and 64-bit Access, and mde must be compiled for each bitness.

However, they should all run nicely on any Windows version from 7 and up.

If this is your scenario, you may wish to set up a series of Virtual Machines each having a specific version of Access installed. This is where Hyper-V comes in. You will need at least 4GB RAM to assign to these, but that should be enough, as you only need one VM running at a time.

Author

Commented:
MASQ
Do you have the accdb in a Trusted Location (Based on either Office settings already set on the same PC or added to the Registry?)
I don't think so, when I try to run it I do get the usual security message, although, giving permission to run ultimately results in the reported errror message

JIM
 The other issue would be references.  If you've used anything (like outlook) and set a reference to it, the target machine must have those programs/references available. The other issue would be references.  If you've used anything (like outlook) and set a reference to it, the target machine must have those programs/references available. 
I am not sure how to set up references when I use the runtime.. The accDB used to create the accDE does have a number of references selected.

Typically when I roll out a compiled version accDE to a machine that has never run the application, as long as o365 is installed, it always runs without setting references.  The difference on this machine is that only the runtime is installed.

ANDERS
Why are you installing a runtime if you have 365?

what happens if you don’t compile it?
I am trying to deploy my application on some windows 7 machines that we have, and these machines do not have 365 licences.  As far as not compiling it, I haven't tried, but its my understand that the runtime can only run compiled versions.  If I'm wrong, that would help me see where its failing..

GUSTAV..
All users on our network are now using a 64 bit Win10 Pro OS and 64-bit Access o365.  I don't think they have a special runtime for o365.. I may be wrong???  The runtime is recognizing the app and running, but then throws the error mentioned.  If I try to start an app compiled as 32-bit as a test, I do get the message that it can not run because it is a 32-bit app.. so I'm sure I have the 64 bit runtime installed.
CERTIFIED EXPERT
Most Valuable Expert 2015
Distinguished Expert 2018

Commented:
All users on our network are now using a 64 bit Win10 Pro OS and 64-bit Access o365.

Then there is no need for a runtime. Just rename the file like application.accdr, and it will open in runtime mode.

Author

Commented:
Gustav... sorry, I was not clear...
All of the users on our network are using Win10 Pro and 64-bit Access o365,
HOWEVER,
I am trying to now run the app on a Windows 7 machine which does not have o365 installed.
In fact, this machine is setup as a robot.. it should boot.. startup.. and then automatically run my app... without any user ever logging in... so I did not pay for a 365 license for the machine.

does the application.accdr work from Windows 7?
CERTIFIED EXPERT
Most Valuable Expert 2015
Distinguished Expert 2018
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
So if I understand correctly.. .in order for an accdb to run the computer must have Access installed... so in that case the accdr can not be used...

I prefer to to use one of my o365 installs on this machine as employees will be responsible for maintaining it.. and I don't wish to risk security concerns...

I have not tried renaming the accde to accdr on the machine with the 2016 runtime installed..

It sounds like the consensus is that there is not a 64-bit runtime that works with an accde file?

Thanks again.
Jim Dettman (EE MVE)President / Owner
CERTIFIED EXPERT
Fellow
Most Valuable Expert 2017

Commented:
<<So if I understand correctly.. .in order for an accdb to run the computer must have Access installed.. >>

 Either the full version, or the runtime.

 Runtime can only do runtime mode, full version can do either and naming a db .accdr will kick the full version into runtime mode (or you can use the command line switch /runtime).

<<It sounds like the consensus is that there is not a 64-bit runtime that works with an accde file? >>

 There is, but an accde needs to be produced with a 64 bit edition of Access.   Lacking source code, it cannot be re-compiled on the fly

Jim.
CERTIFIED EXPERT
Most Valuable Expert 2015
Distinguished Expert 2018

Commented:
You missed most of it ...

An accdr file is just a renamed accdb or accde file, and will run where these would run - with an Access runtime or a full Access install.
With a full install, an accdr will run as runtime.

An accde is a compiled accdb - in one bitness only - 32 or 64 bit. Rename it as accdr and it will run in runtime mode.
CERTIFIED EXPERT

Commented:
I have a MS Access application which I compile into an accde using Access o365.  When I attempt to run the application from my Desktop computer with MS Access o365 installed everything works perfectly....HOWEVER..

Which year???

If your program was done in Access 2019 , then runtime 2016 can never open that , you just have to use Access 2019 365, then it will work.



John TsioumprisSoftware & Systems Engineer
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
I know that you will try several workarounds but if everything fails the recipe i used in the past was just simple but it takes some time.
So, you have a machine that doesn't has O365 and you want to run Access.
1st take a full image backup (just in case)
2nd uninstall runtime
3rd Install O365 in trial mode
4th pull the .accdb , what errors pop out ?
5th fix the errors ,try the .accde ,is it OK ?
6th uninstall - wipe clean trial
7th install Runtime...it should run...UNLESS you are referring to a O365 "element" e.g. you are referencing Outlook but since no O365 no Outlook.

Author

Commented:
I never did get the runtime to work with my 64-bit compiled accde application.. I did use the o365 runtime.. and also the same bitness.. but it did not work.

My solution was to buy another license for o365 and to use it.  The app runs fine with o365 installed.
I did have a reference to outlook.. so that may have been the reason.. however, the no current record message makes me think that was unlikely the cause.

Thanks experts!
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.