I tried connecting to MS Access 2016 database using OLEDB 12 and it worked. However after a few connections(sequential), I noticed that my code got stuck while opening the connection. It would neither fail or exit, just stuck.
I have that that I am properly closing the connection after use.
When I installed Access 2013 runtime and used OLEDB 15, the issue was solved.
But I am unable to install this runtime on all my nodes in production.
Is there some known issue on using OLEDB 12 to connect to Access 2016. Is it solvable by some code fix ir will I have to move to Access 2013 runtime.
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'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
When running an existing mail merge I receive an error in one of my machines: Class not registered
No real indication of what is not register
The only thing I can find different between working and non-working machines is in the Data Link Providers. in the non-working machines I am missing 'Microsoft Office 15.0 Access Database Engine OLE DB Provider'.
I assume these documents were created using this provider and my trouble machines does not have it.
Any tips for how to get it?
Thanks!
The solution was to install the Access 2013 Runtime. This made 'Microsoft Office 15.0 Access Database Engine OLE DB Provider' available in Word 2016. Although the default application to launch .ACCDB became the runtime, so I needed to change the default back to 2016.
Here's a link to the 2013 Runtime: https://www.microsoft.com/en-us/download/details.aspx?id=39358
We are planning to upgrade from SQL Server 2014 and Visual Studio 2013 to SQL Server 2016 and Visual Studio 2015.
The error message:
[IBM][System i Access ODBC Driver]Communication link failure.
comm rc=25202 - CWBCO1034 - SSL error, function returned 25202
Background
We have an SSIS project which connects to an IBM DB2 server and retrieves data. This has been working for years.
The working setup looks like this:
Windows 10
Visual Studio 2013
SQL Server Data Tools for Visual Studio 2013
IBM i Access for Windows, version 7 Release 1
A DSN pointing to the IBM DB2 server
ADO.NET Connection Manager with ODBC Data Provider pointing to the DSN mentioned above.
SSL enabled on the DSN.
If we on the same machine use Visual Studio 2015 and subsequently SQL Server Data Tools 2015, it no longer works. Everything else is the same!
As soon as the package is opened and SSIS starts to validate the connection managers the error message arises.
I am using windows 7 64 bit,VS 2010 and MS Office 2010. Trying to build an ssis pkg using an excel source, the problem arises as below.
Could not retrieve the table information for the connection manager 'Excel Connection Manager'.
Failed to connect to the source using the connection manager 'Excel Connection Manager'
I found some solutions on internet, tried these steps by
1) installing the MS access database engine 2010 redistributable_x64.exe. I restarted the system, But still the problem persists. i couldnt find the provider in the list of providers in the oledb source and so selected the jet 4.0 oledb provider and changed the extended properties to Excel 12.0, then i get the following error:
Test connection failed because of an error in initializing provider. Could not find installable ISAM.
and also if i use excel source, its throwing me an error as given above on the top.
2) Also, changed the run 64bit runtime to false and also back to True again.
3) tried to change the platform of the project , but it is disabled.
Could yopu please help me. Thanks in advance.
You need to install the 32 bits provider.
Even though your windows is 64 bits, the SSDT development environment is a 32-bit environment. The reason why you cant find the provider in the list of providers is because it only shows 32-bit data providers. You can only see 64-bit providers that have a 32-bit version available on the development machine.
Though its bit late but might to very helpful for other guys.
Visual Studio 2010/2012 comes with 32-bit version only and hence it cannot use ACE OLEDB 64-bit version, which comes with installation of office 2010 64-bit version.
So the solution here would be uninstall 64-bit version office 2010 and install it's 32-bit version. Re-try to add the excel connection manager.
This has resolved my issue and hope for other guys as well.