This is not a progrmaing question, but I am sure MS Access developers will soon hit this problem
Situation : PC has MS Office 365 Installed (Home or small Business version) which does not include MS Access 2016.
Try : Instating MS Access Runtime 2016.
Problem : Access runtime installation gives error saying, cannot install same conflicting application.
Question : Is there any way we can install both MS Access runtime 2016 and Office 365?
I develop Access front ends, which I then compile (.accdr) and distribute to my users. Users does not have MS Access installed on their PC. They just have Access Runtime.
My current temporary solution : Ask users to install Access runtime 2013 instead of 2016.
Note: All the office versions are 32 Bit (X86)
https://blogs.office.com/2015/12/16/access-2016-runtime-is-now-available-for-download/
Note for Office Click-to-Run (C2R) users:
As stated in the past, Office C2R and MSI of the same major version cannot be installed side by side. Currently, if you are using Office/Access 2016 C2R, we recommend that you install Access 2013 Runtime MSI if you need a side-by-side setup. The two versions are functionally equivalent, and this installation should work smoothly.
—The Access team
So yes, 2013 is the solution.
Also here .
The reason for your problem is that
Office 365 is Click-To-Run-based (C2R) and
the Access 2016 Runtime is MSI-based
and they cannot both be installed on the same machine.
Recently, Microsoft released the Office 365 Access Runtime, which is Click-To-Run-based and, thus, compatible with Office 365.
Download and install Office 365 Access Runtime
Note that this runtime is not compatible with Office 2019 (or 2016 C2R, as far as I know). Currently, there is no runtime compatible with Office 2019, but Microsoft's response to this UserVoice entry suggests that one might be released in the second half of 2019.
Don't use the MS Office 365 Online from your account. It seem that there are some problem with it, it lack all the ODBC driver. I searched everywhere for the solution: Uninstall/reinstall Office 365 (tried with Microsoft Access Runtime 2010/2013/2016). Well, you can install Office 365 first then the Access Runtime 2013 but it still doesn't work, like you can't open your *.mb or *.accdb....
Luckly, i try the last time with the MS Office 365 OFFLINE and it work.
Hope this response come into hand of people that's in the same situation as me.
Related
I have here a specific application I am forced to use. This application uses Access as data storage.
This application is older and was once developed for Office 2013. Our company computers have now Office 2016 installed, with Access 2016.
After the installation of Access 2016 this application stopped running. It hangs immediately after start.
So i installed Access Runtime 2013 and application first worked fine. But as soon as I open Access 2016, there is a repair run installing something in the background and application again stopps working. After executing Repair on Access Runtime 2013, it works again until Access 2016 ist again opened.
After checking the dump of this Application I see that after running repair of Access 2013, Office15-DLLs are used. After starting Access 2016 and repair run, Office16-DLLs are linked and application stops working.
All those repair runs take minutes, so they are very annoying, as I often have to switch between both applications.
Is there any other / better way to handle it? I tried to set Runtime 2013 into the PATH of my application, no changes. Can I somehow force the application to use Runtime 2013 instead of Access 2016?
Thanks!
I have upgraded my access app to 64bit and I am in the process of updating client pcs to 64bit runtime. I have updated dozens of pcs with 32bit office by using a different version of 64bit runtime (for instance, 2016 64bit runtime with 2013 32bit office, and 2013 64bit runtime with 2016 32bit office). However, while updating a client today none of their pcs will allow the update. They have office 2013 standard (32bit) and trying both 2016 64bit and 365 64bit access runtime fails with the error below. What could be different with these pcs? This is happening on both Windows 7 and Windows 10 pcs.
Found the solution - there was some sort of an error on the install of office 2013 (whenever it was installed). The solution was to start the office 2013 setup again, and cancel at the first prompt (no need to uninstall first). This fixed the error and allowed 2016 64bit access runtime to be installed.
Microsoft article explaining the above solution is here
I've made an application on an MS Access 2016 with 365 subscription and deployed an .accde file. When I try to open that file on another PC with runtime installed (tried with 2016 4288-1001 64bit and 2013 64bit) I get an error saying "Database you are trying to open requires a newer version of Microsoft Access".
I know that are some issues related to runtime and 365, but some people said that using runtime 2013 solved their problem (but not mine).
Anyone have a solution for this?
The problem was that some of my table fields data was set as "Large Number".
I don't know why, but Access Runtime 2016 can't read this data type, changing the fields to "Number" made the deployed ".accde" open normally.
Source: https://support.microsoft.com/en-us/help/3208802/-database-you-are-trying-to-open-requires-a-newer-version-of-microsoft
I have a Access 2003 database that I want to store in source control on TFS2010. I'll be using the Team Foundation Server MSSCCI Provider 2010. Are there any rules for which versions of Access can create a database from that source? It's possible that Access 2010 and 2007 will be used to edit the source control. I'm curious as to if I should limit the versions of Access touching the source code to just a single version of Access.
The site of MSSCCI states to support Access 2007: http://visualstudiogallery.msdn.microsoft.com/bce06506-be38-47a1-9f29-d3937d3d88d6
On the same site, two other references from users can be found. One is stating that this version also works for Access 2003. Somebody else is experiencing that this version of the MSSCCI does not work for Access 2010.
A save bet would be to start your efforts with Access 2003, or if possible better with 2007. At least do an experiment with saving some 2003 stuff and opening it again with 2007 and vise versa. In time, I guess that support for Access 2010 will show up and you can continue from there on with newer version.
I am making a windows application that uses MS Access 2007 as backend database. To install this application on other machines, the machine need to have MS Access 2007 or MS Access Runtime 2007. As MS Access Runtime 2007 is redistributable I decided to bundle it in my MSI.
Problem is that in Visual Studio 2008, in prerequisite options I can not find MS Access Runtime 2007 as an option, rather I have Microsoft Office 2007 Primary Interop Assemblies. So I am not sure how to proceed.
Someone's feedback with previous experience on the same will be helpful.
If you are only using an ACCDB to store data then you don't need Access 2007 or the Access 2007 run time. All you need is the Access Database Engine or Microsoft Access Database Engine 2010 Redistributable
However I can't answer the rest of your question.