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.
Related
I plan to package and deploy an ms access .accdb that I've created in access 2016 using SSE Setup to a user that has a full version of access 2003. If the package installs Access 2016 runtime, will it corrupt the 2003 software, or will it only affect the accdb that I am packaging
I'm trying to connect to an Access database via a UDL file. I'm wanting to generate a connection string so that I can connect to an access database via ADO.NET. It's been a few years since I've tried to do this.
I have Visual Studio 2015 Pro and Microsoft Access 2016 installed on my Windows 10 x64 pro machine. When I create a .udl file I have the following available options:
Microsoft OLE DB Provider for ODBC Drivers
Microsoft OLE DB Provider for Search
Microsoft OLE DB Provider for SQL Server
Microsoft OLE DB Simple Provider
MSDataShape
OLE DB Provider for Microsoft Directory Services
SQL Server Native Client 11.0
I think that in years past I would also see Microsoft Jet 4.0 OLE DB in this list. From the research I've done I think that Jet 4.0 is deprecated and that I should be using the Access Database Engine. I find the following versions that I think are that:
Microsoft Access Database Engine 2010 Redistributable
Microsoft Access 2013 Runtime
Microsoft Access 2016 Runtime
I downloaded the x64 version of Microsoft Access 2016 Runtime and when I try to install it I get the following error:
We can’t install the 64-bit version of Office because we found the following 32-bit programs on your PC:
Office 16 Click-to-Run Extensibility Component
Please uninstall all 32-bit Office programs, then retry installing 64-bit Office. If you want to install 32-bit Office instead, please run the 32-bit setup.
I've tried the 32-bit version of the Microsoft Access 2016 Runtime and I get the same message:
We can’t install the 32-bit version of Office because we found the following 64-bit programs on your PC:
Office 16 Click-to-Run Extensibility Component 64-bit Registration
Please uninstall all 64-bit Office programs, then retry installing 32-bit Office. If you want to install 64-bit Office instead, please run the 64-bit setup.
I've tried closing all open Microsoft Office and Visual Studio applications and I get the same error. Am I installing the right component? Any way to get it to install correctly?
You probably miss the ACE driver listed here - and only this, not the runtimes:
Microsoft Access Database Engine 2010 Redistributable
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 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 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.