Access announces removal of Salesforce ODBC driver in October 2025
MS Access 2019 (and newer) ships a licensed Salesforce ODBC driver from InsightSoftware that will lose sustaining support after June 30th, 2026. But because we can no longer provide updates for the driver, the Access team has decided to accelerate the removal of this driver and remove it from the product in October 2025. Applies to: Access 2019 volume licensed and Enterprise plans Access 2021, Access 2024, and Microsoft 365 subscriptions Access 2021 and Access 2024 as part of the Office 2021 and Office 2024 perpetual licenses (standalone versions) The Salesforce ODBC driver bundled with Office includes shared libraries such as: libcurl.dll libcrypto-3.dll libssl-3.dll These libraries are located under the following path: Program Files\Microsoft Office\ODBC Drivers\Salesforce. They may also be present in different locations. Drivers installed by Office and used to access your Salesforce data will be removed on permanently on October 28, if you are using Access as part of a Microsoft 365 Apps monthly version and on November 11 if you are on the semi-annual release. For customers using perpetual Access 2019, 2021, or 2024, the drivers will be removed on November 11. You do not need to manually remove the drivers. Access currently doesn't have a way to talk directly to the Salesforce APIs so customers must continue to use the standardized ODBC driver framework that we currently support. Customers can independently purchase the Simba.DLL driver if needed from InsightSoftware. There are also other vendors that offer a Salesforce driver. Simba driver from InsightsSoftware https://insightsoftware.com/simba/ ODBC driver from devart https://www.devart.com/odbc/salesforce/ Salesforce integration from boomi https://boomi.com/solutions/application/salesforce/ Salesforce driver from cdata https://www.cdata.com/drivers/salesforce Once you purchase and install the driver, Access can connect to your Salesforce external data source. On the External Data ribbon, choose New Data Source > From Other Sources > ODBC Database We will provide more updates when available.
ODBC Drivers + No Shortcut Apps
Hi All, I am new to MSIX, Could you please provide some information for the below points. 1. Is it possible to create MSIX package with the installer having ODBC Drivers with out any Shortcuts/EntryPoints? 2. How to Handle User settings/Configurations which stores in AppData or in HKCU 3. Can anyone provide the user guidance or any demo/links to use PsfTooling 4.8? Thanks in Advance. Thanks & Regards, Siva
Getting Illegal character from SQL DB
We are getting Illegal character (?) while retrieving a nvarchar field(TEMP-WRK-INFO) from a table in a cobol module. Below are region details:- Linux version - RHEL 8.3 MSSQL version - 2019 Initially, we got illegal character while converting the hex value to ASCII value. For example, when the amount of 894.55 is moved to TEMP-WRK-INFO, then hex value of (89 45 5C) is converted to ASCII as (?E\). This issue occurred as extended ASCII value is not converted correctly. We had a fix for this issue by changing the LANG to en_US.CP1252 in environment settings, then it worked for all extended ASCII value except for 81 and 90. When the hex value has the combination of 81 or 90, then we get the illegal characters. Same logic is working fine in windows environment.
Microsoft Access Issue ODBC driver postgreSQL
Hello, I am trying to import data from a postgreSQL database to access, but I am getting an error when clicking on the table to import, the error is saying "the size of a field is too long". I have tried modifying settings in the ODBC driver but nothing resolves the problem. Is there anyway I can resolve this? Thanks.
SQL Server 2012 Native Client
Microsoft SQL Server 2012 Native Client is being flagged an obsolete software and will stop receiving security updates starting July 12th, but I have done a lot of searching on the internet and getting a mixed results on whether this is true or not. So I figured I would ask here to see if anyone else is dealing with this situation and what conclusion can be made here. For example, Microsoft has a blog post regarding the software that says the software is obsolete on July 12th, which can be seen here: https://techcommunity.microsoft.com/t5/sql-server-blog/snac-lifecycle-explained/ba-p/385381 However, I have been told that there is an exception to the rule that says it is supported "in SQL Server 2012 through 2019 until their respective end-of-support lifecycles", described at the bottom here: https://docs.microsoft.com/en-us/sql/relational-databases/native-client/applications/support-policies-for-sql-server-native-client?view=sql-server-ver16 So I guess my ultimate question is: Will "SQL Server 2012 Native Client" still receive security updates post July 12th of this year?
