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.
SQL Statement lenght limits for SQL Server Native Client and ODBC Driver for odbc
Hi, I have an application that use SQL Server from 2012 to 2022. It executes SQL Statements with up to 88.000 characters With SQL Server Native Client 2012 it works, however with ODBC Driver 18 for SQL Server it doesn't, ODBC limit the SQL Statement up to 65000 characters, I noticed this in SQL Profiler I will need ODBC Driver for SQL because SQL Native Client doesn't support sql server 2022 I don't know if there is a solution to this issue I'm using DELPHI and FireDAC for the development and I don’t need create a DNS to connect the application to the database, I set the necessary params to FireDAC so it does the connection thanks for your suppor
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?Lesson Learned #371: Playing with the ODBC tracing file: connecting to the database
A few days ago, I encountered a case where our customer asked about the process of reading and reviewing all the ODBC traces generated by their application. In this example, I would like to share the lessons I learned while connecting to the database.
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?
