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!
Related
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
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.
I have developed a access 2007 database that is hosted on the clients server. They input data 24/7 in house, and enjoy the fast speed of the local connection. However, they are now wanting to view this data on a mobile device. I would like to be able to create a new Access 2013 web app, and have my current access 2007 database transfer data to a hosted server somewhere, where the access 2013 web app will run from. There won't be any need to add/edit/delete data from mobile, just view, so that saves me a lot of trouble with having to convert all my vba. I just have no idea how to go about this, or if it is possible. If I use a hosted sharepoint server, can I add my web app there, and be able to transfer data to the server to view?
Unfortunately Access 2013 web uses SQL Azure, and starting with Access 2010 is when support for Azure was introduced. I not at all sure you can thus use Access 2007 to connect to a 2013 web database (you should be able to use 2010 or 2013).
I think in this case you might consider just building a simple asp.net web site and then have Access 2007 send some data to that site (assuming the site allows external ODBC connections – these are becoming harder to find these days).
As I alternative I suppose you could upgrade to Access 2013, and for existing desktops deploy the FREE 2013 runtime. This should in theory allow you to keep your existing application, and also connect to the 2013 web application you publish. You have to sort up the users permissions here.
So while the Access client(desktop edition) can link to published Access web applications, I don't believe that Access 2007 can be used since it does not have support built in for using SQL Azure like 2010 and 2013 does.
I'm using Access 2013 32 bit on Windows 8.1 64bit. I'm attempting to test my application in the runtime mode but it causes Access to crash early in the application start phase. It doesn't appear to matter what code is running as it crashes when I try to open a file that has only tables (no macros, forms, or code modules).
I've tried running Windows Update and there doesn't appear to be any updates available. But when I look to see what updates were installed over the last day or so (I just installed Office 2013 yesterday), I can't tell that any Office updates have been installed.
Has anyone else seen this problem? Any solutions other than using something < 2013?
I have an Access database in source control on TFS that I need to pull down onto another machine (XP, Office 2007). I have the Team Foundation Server MSSCCI Provider 2010 installed and I can successfully see the source. However, when I try to have it created it fails, giving me this error:
Failed to create a new database on a Team Foundation project.
Any idea what I've done wrong on this machine?
I think the solution to this was that I had sent the database up to TFS from Access 2010, but was trying to pull it down to another machine with Access 2010. I thought the two versions shouldn't matter, but sending it up to TFS in Access 2007 and bringing it down in Access 2007 and Access 2010 appeared to work.