Since the Monthly Channel Office 365 Update to version 1912 on December 19, 2019, the ODBC connection in our MS Access application appears to be broken. Uninstalling the version 1912 update fixes it. I don't see any information about this problem on the Release Notes for Office Insiders web page.
Related
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 have an app that's been working fine in 32 bit using the connection string:
Driver={Microsoft Access Driver (*.mdb)}; Dbq=MyDatabase.mdb;
using ADO in C++ on a PC with no Office installation.
I have converted it to x64 and I believe I need to install some form of Access drivers no matter if the host PC has x64 Office installed or not. So I grab Microsoft Access Database Engine 2016 Redistributable and install it.
In general everything works OK but certain SQL queries are failing. Most noticeably ones that use LIKE '%somevalue%' - now I understand that % is ANSI-92 but it's been working fine as I say so assume that's ADO related (I could change this to ALIKE I guess).
What I don't understand is if I install the Access Database Engine 2010 then all works as expected. It seems that something is different in the Access Database Engine 2016. I did look for some release notes/breaking changes but couldn't find anything.
So my question is are there changes in the way SQL is parsed in Microsoft Access Database Engine 2016 and should I simply get customers to install the 2010 version?
Note: the other query that seems to be failing is a table with a Yes/No field. I have a query that checks: field <> 0 and this throws an exception.
Update: If I install the Microsoft Access 2016 Runtime then all seems to work. So the issue seems specific the Microsoft Access Database Engine 2016
So in summary:
No Office Installed: Installed Access 2016 x64 Database Engine: Query FAILS
No Office Installed: Installed Access 2010 x64 Database Engine: Query PASSES
32bit Office Installed: Installed Access 2016 x64 Database Engine: Query FAILS
32bit Office Installed: Installed Access 2010 x64 Database Engine: Query PASSES
x64 Office Installed: Installed Access 2016 x64 Database Engine: Query PASSES
Where the Query is:
SELECT * from sometable WHERE somefield LIKE '%ABC%';
The setup is:
Window 10 Version 1909
32 bit Office: Microsoft Office MSO 16.0.12325.20280 32bit
64 bit Office: Microsoft Office MSO 16.0.12325.20280 64bit
Access database engine (x64) from here: microsoft.com/en-us/download/details.aspx?id=54920
My app is x64
Are you using SQL Server as the backend database, or Access?
In SQL Server % is the wildcard symbol.
With a pure Access environment, the wildcard standard is usually *
There may be a setting to change this, but I can't recall.
reference: https://support.office.com/en-us/article/like-operator-b2f7ef03-9085-4ffb-9829-eef18358e931
I have an issue on our SSRS 2016 printing from Dynamics CRM application. Reports render correctly, but every time I want to print by clicking the print icon, I am prompted to install the ActiveX print control.
Note
As a local admin user, I can install it and I can print, but I have to do it every single time. And normal users do not have that option. Also when I open manage add-ons I can see that it is installed.
Running:
Microsoft SQL Server 2016 (SP1-GDR) (KB4019089) - 13.0.4206.0 (X64) Jul 6 2017 07:55:03
Copyright (c) Microsoft Corporation Enterprise Edition:
Core-based Licensing (64-bit) on Windows Server 2016 Standard 6.3 <X64>
(Build 14393: ) (Hypervisor)
enter image description here
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.