470,870 Members | 1,756 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,870 developers. It's quick & easy.

Access 2013 Runtime

We have Office365 / Sharepoint online / Exchange online in our organization. I am the only one with the E3 subscription which gives me Access. I have a database that needs to be made available to other users on our office network. I discovered that Access 2016 runtime cannot be installed side-by-side with Click To Run (CTR) Office365, I installed Access 2013 runtime which is supposed to work. I have not split the database yet for network access but am working to get the first client running. I copied the database to their desktop and attempted to open it. I entered the trusted location into the registry to get rid of the security error but all that displays is a blank screen. I do not have a autoexec macro in the database to open the main form of the database. I'm assuming that is one of things that has to be completed first or is there something else that needs to be done as well.
Jun 21 '16 #1
7 1912
Seth Schrock
2,965 Expert 2GB
You must have a form open automatically for Access Runtime to work. I do it through the Options>Current Database>Display Form. I've never tried it through the AutoExec macro, but I suppose it would work just the same.
Jun 21 '16 #2
Thanks, that is what I was looking at just before I went home from work yesterday. I did add that to the Access options settings but still only shows a blank screen when double clicking to open the database.
Jun 21 '16 #3
Seth Schrock
2,965 Expert 2GB
That is very strange as it always works for me. You might double check that the file that is being opened does in fact have that setting and it isn't a different version of the file.
Jun 22 '16 #4
Correct me if I'm wrong but I had the database open, went to the Access settings Options>Current Database>Display Form and entered the name of the form to load then saved the database. Correct? if correct, Windows 10 issue maybe? or the 2013 runtime fails when run under Windows 10 with Office365 2016?
Jun 22 '16 #5
Very odd thing this is. Yesterday this would not work on the client machine in question but right after I posted the previous reply I went and checked again and now it opens fine. Go figure... At any rate, thanks for help...
Jun 22 '16 #6
Seth Schrock
2,965 Expert 2GB
You are welcome. Good luck on your project.
Jun 22 '16 #7
5,463 Expert Mod 4TB
jalbright1957 - At least a Restart; however, better, a Cold Reboot will often fix these types of bugs... sometimes the machine just needs a fresh start... shrug. :-)
Jun 28 '16 #8

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

By using this site, you agree to our Privacy Policy and Terms of Use.