Access bug fixes — Versions 2511 through 2601
Version 2511 (Build 19426) Bug Name Issue Fixed Query Design view showed incorrect joins after selecting SQL text When using the Monaco SQL editor with a query containing multiple joins, selecting text in SQL view with Ctrl+A and then switching back to Design View could trigger a spurious alert and cause one of the joins to appear removed in the design grid. The underlying SQL wasn't actually affected, but the Design view displayed incorrect join information. This is corrected so that switching between SQL view and Design view preserves all joins accurately. Version 2512 (Build 19530) Bug Name Issue Fixed Datasheet forms with nested subforms showing errors after system changes When using datasheet forms containing nested subforms on systems where a system change occurs — such as disconnecting and reconnecting a Remote Desktop session — Access could display a GDI error. This happened because collapsed sublists held references to system brushes that were destroyed during the system change. This is fixed so that all sublists properly handle system resource changes. F4 key did not open the Properties pane in the Query SQL editor When the Monaco SQL editor was enabled, pressing F4 in the Query editor's SQL view didn't properly open the Properties pane. Instead, the pane would either flash briefly or appear incorrectly positioned in the top-left corner of the screen. The F4 shortcut now correctly opens the Properties pane in SQL view. Pressing F5 in the Query SQL editor cleared all SQL text When using the Monaco SQL editor in the Query designer, pressing F5 (Run) could clear all the SQL text from the editor. This is fixed so that running a query with F5 no longer affects the SQL text in the editor. Text not visible when renaming items in the Navigation Pane in dark themes When using the Black (or other dark) Office theme, renaming an object in the Navigation pane resulted in text that was nearly invisible due to insufficient contrast. The rename text box now uses appropriate colors that provide sufficient contrast in all themes. Advanced Filter/Sort opened a standalone query window instead of a filter window When opening a table in Datasheet view and selecting Sort & Filter > Advanced > Advanced Filter/Sort from the ribbon, Access incorrectly opened a full standalone query design window instead of the expected limited filter query window. The filter query window includes a Toggle Filter button to apply the query as a filter. This is corrected, so the command opens the proper filter window. Refreshing an Access ODBC connection in Excel returned an error When refreshing an ODBC connection to an Access database from Excel, users could receive the error "Operation is not supported for this type of object." This is resolved so that Access ODBC connections refresh successfully. Please continue to let us know if this is helpful and share any feedback you have.
ODBC from Access to SQL Server database - query timeout expired
I am having issues connecting to a database located on a SQL Server 2022. When creating the connection all test gives OK. But when trying to connect, it fails with: ODBC--call failed "Query timeout expired" If I don't define the database, then Access connects to master db and lists the tables that I can access. So it seems the connection to the server itself is ok. Tried ODBC SQL server driver, SQL Server 17 and 18 odbc driver, all same results. Same database on SQL Server 2014 also does not work for my user, but another user has previously been able to connect to old database, but seems something is missing either client-side or server option in the new setup?
Access with SharePoint List link - ODBC
Hi all, I needed to get some of the SharePoint List data into Python, Matlab etc. As there were no dedicated connectors that would also combine well with SSO, I used ODBC to create a connection with Access DB. In this Access DB I linked the SharePoint list. It allows me to use basic SQL on sharepoint data from the code. That works reasonably well when it comes to running Select and Delete queries. However when it comes to Inserts it has encountered an issue when a duplicate record is added to a unique column. This breaks the linked connection in Access Db. To restore it I need to open Access Db and resolve the conflicts there or refresh the SharePoint link. Is there any way to do through some command without opening the Access Db?
Problem to migrate simple Access mde app and Microsoft Sql Database to another PC
Hello there, Im struggling to move an old Access app, which runs on a windows server 2003, to my Windows 10 PC, The app is run from the Server desktop via mde file and is connected to a microsoft SQLEXPRESS database installed locally on the server, I installed locally on my pc windows 10 Microsoft Sql express, and changed the hostname of my PC setting "SERVER". I can access the tables and the database seems to work, but when I launch the "example.mde" file from my computer the application fails and cannot find the database asking me for the path.. if i click continue with trusted authentication it ask me again for every move i make .. I don't know how to specify the data source or connection string for the database on the new machine, I believe this is about the ODBC driver, attached the error I get. https://i.stack.imgur.com/ZWzme.png Thanks in advance for the helpAccess ODBC does not recognize automatic client reroute
Hi, I have an ODBC connection to a DB2/LUW database in MS/Access (2016) and am trying to implement ACR (Automatic Client Reroute). I have added the following (bold) to my db2dsdriver.cfg file: <database name="MYDBASE" host="DBHOST1" port="60000"> <parameter name="hostname" value="DBHOST1"/> <parameter name="port" value="60000"/> <parameter name="AltHostName" value="DBHOST2"/> <parameter name="AltPort" value="60000"/> <acr> <parameter name="enableAcr" value="true"/> <parameter name="maxAcrRetries" value="10"/> <parameter name="acrRetryInterval" value"1"/> <parameter name="enableseamlessACR" value="true"/> <parameter name="enableAlternateServerListFirstConnect" value="true"/> <alternateserverlist> <server name="otherserver" hostname="DBHOST2" port="60000"/> </alternateserverlist> </acr> </database> I have tested this on my machine and it successfully falls over to the alternate server when the primary server is unavailable. However, when I attempt to connect to the database in MS/Access, I get a connectivity error (SQL30081N) Has anyone worked with MS/Access and ACR? Thanks!
“Operating system is not presently configured” error with Access ODBC
I get the following error when I try to connect to Microsoft Access Database via Python. The code has been working all this time and only started popping the error today. Can someone please guide me what may be the problem occurring now? I tried doing this https://stackoverflow.com/questions/63899661/operating-system-is-not-presently-configured-error-with-access-odbc even after removing the “Office 16 Click-to-Run Extensibility Component 64-bit Registration” my problem isn't getting solved. import pyodbc as pyo import os #print(pyo.drivers()) filename='//MCISERVER1/TestData/access/Proof.mdb' full_file=os.path.abspath(os.path.join('data',filename)) print("opening access") Driver='{Microsoft Access Driver (*.mdb, *.accdb)}' access_driver=['MS Access Database'] try: cnn=pyo.connect(driver=Driver,dbq=full_file,autocommit=True) except pyodbc.Error as ex: print("Error connecting") cursor=cnn.cursor() sql="select * from [ERT ITRON] as e where e.SO='7888'" cursor.execute(sql) for row in cursor.fetchall(): print(row) print("success") cursor.close() cnn.close() print("connection closed")
