Once set up using the correct ODBC manager, the database user was set up with the wrong password to match our software.ģ. The runtime version installed is 32-bit.Ģ.
![ms access runtime error 3122 ms access runtime error 3122](https://community.dynamics.com/cfs-file/__key/communityserver-discussions-components-files/33/3122.2.png)
The PCs were originally set up with the DSN in the 64-bit ODBC manager rather than the 32-bit. Has unusual problems with database server migrations that should be straightforward.ġ. It was a mixture of things in the end! There have been a number of things we've had to correct on the way through so I'm posting this last response to hopefully help anyone else who Many thanks for your assistance with sorting out our customer's issues.
MS ACCESS RUNTIME ERROR 3122 FULL VERSION
The IT support team are currently installing the full version of Access on the PC to see if it is a runtime related issue but we would be grateful for any suggestions if anyone has seen anything similar using Access 2013 with SQL Server 2016. We can extract data using the full version of MS Excel (2013) on the same PC, but the databaseįE will not successfully connect to the data. We have checked the DSN connectivity - Test Successful every time. The PCs on site which are running Runtime Access however, return an ODBC Call Failed error. This connects with no problems to the new server after updating the DSN on that machine. We have a development PC on site with the full version of Access 2013 on. Server, applied to the restored database and connections tested. The user details have since been set up with us for the new I believe all PCs are configured the same (although am awaiting confirmation of that from their IT support) - the data was backed up and restored into the new database server as far as I am aware.
![ms access runtime error 3122 ms access runtime error 3122](https://i.ytimg.com/vi/nn0sP5HDiG0/maxresdefault.jpg)
They were running an Access mde application which we built using Access 2007 but is running on site in Runtime 2013.
![ms access runtime error 3122 ms access runtime error 3122](https://www.mdpi.com/applsci/applsci-10-00398/article_deploy/html/images/applsci-10-00398-g001.png)
We have a client who has upgraded their back end SQL Server database from 2014 to 2016 this week.