Office v2508 feature update (new vbe7.dll) breaks library compatibility with LTSC VL versions
Since the Jan 2026 updates, some `accde` or `mde` libraries built with the semi-annual enterprise channel (v2508, Build 19127.20484) can no longer be used with the volume-licensed version of Office LTSC (tested with the Jan 2026 release of Office 2024 LTSC VL, v2408, Build 17932.20638). The reason for this seems obvious: The v2508 feature update contains an updated vbe7.dll. Apparently, this change is backwards-compatible (code compiled with the old dll will run with the new dll) but not completely forwards-compatible (code compiled with the new dll might not run with the old dll, even if the new RegExp class is not used). That's a problem for us. We can't just tell our customers to upgrade, because those with an Office 2024 LTSC volume license already use the latest version available to them. Does Microsoft consider this a bug or "by design"? If the latter, what is Microsoft's recommendation for software vendors who want to build software that runs on all currently-supported versions of Access? We currently plan to work around this issue by installing v2502 of the semi-annual enterprise channel on our "build VMs" (32 and 64 bit) and use those to build our software. (Reverting dev machines to an old Office version is not an option for obvious security reasons.) Repro On a PC with v2508 or newer: 1. Create a new mylibrary.accdb with a module with the following code: Public Function GetColorCode() As Long GetColorCode = vbRed End Function 2. File/Save as/Create accde. 3. Copy mylibrary.accde to a PC with v2507 or older (for example, with the current version of Office 2024 LTSC volume license). On a PC with v2507 or older: 4. Create a new database. 5. Create/Module/Tools/References 6. Add a reference to mylibrary.accde 7. Add the following code to the module: Sub Test() Debug.Print GetColorCode() End Sub 8. Debug/Compile Expected result: The database compiles. Actual result: "Compile error: Can't find project or library". The "references" window opens automatically and highlights "mylibrary". Notes We are not library developers, but we are still impacted by this issue, since the software we ship consists of a (modifiable) startup mdb referencing an (unmodifiable) mde containing the business logic. If you want to try to reproduce this issue but don't have a volume license of Office 2024 LTSC lying around (we certainly don't), you can install a trial version with the Office Deployment Tool and the following configuration file: <Configuration> <Add OfficeClientEdition="64" Channel="PerpetualVL2024"> <Product ID="ProPlus2024Volume"> <Language ID="en-us" /> </Product> </Add> </Configuration>The return of the performance leak - this time with subreports
Anyone remember the v2405 bug that caused loading and closing forms to become slower over time? We found something similar in the current release (tested with semi-annual 2508 (19127.20484)), just with sub reports instead of forms. Here are the repro instructions: Repro instructions Table 1. Create a "numbers" table with a PK field "nr" (Long Integer). 2. Fill it with the numbers from 1 to 100: Dim i For i = 1 To 100 CurrentDb.Execute "INSERT INTO numbers (nr) VALUES (" & i & ")" Next i Sub report 3. Create a new empty report in design view, using the "numbers" table as the record source. 4. In the detail section, add two text boxes "Text1" and "Text2" next to each other, both with the "nr" field as their control source. 5. Reduce the size of the detail section to one "row", containing just the two text boxes. Remove the page header/footer. 6. Add an Format event handler to the detail section with the following content: Me.Text2.Visible = False 7. Save the report as "sub". Main report 8. Create another report "main", which contains nothing but the "sub" report as a subreport in its detail section. Set the record source of "main" to "SELECT * FROM numbers WHERE nr <= 10" Reproduce problem 9. Create the following method in a module: Sub report_loop() Dim i As Long Dim start_time As Single Dim report_name As String Dim path As String report_name = "main" For i = 1 To 40 path = Environ("Temp") & "\testreport.pdf" start_time = Timer DoCmd.OpenReport report_name, acViewPreview DoCmd.OutputTo acOutputReport, report_name, acFormatPDF, path DoCmd.Close acReport, report_name Debug.Print Timer - start_time Next End Sub 10. Run report_loop. Observe that each report export gets slower and slower. Analysis Compare the first and last number in the immediate window: on my machine it's 0.4s for the first report and 2.3s for the last. Note that if you run report_loop again, it will start slow! In other words, each report export causes MS Access to "leak performance" that is only regained after restarting Access. We were able to reproduce this issue with Microsoft 365 semi-annual channel, Version 2508 (19127.20484). I'll do more tests tomorrow and try different older versions to find out when this bug was introduced. Workarounds If you move the visibility code from the Format event to the Print event, the problem still occurs, but slower (0.4s -> 0.72s instead of 0.4s -> 2.3s). The workaround that worked for us was to use =IIf(...) in the control source instead of modifying the visibility. Obviously, that only works for text boxes, not for lines or other controls.
Database in an "inconsistent state" and other errors
Hello. I was directed here for help by Microsoft Tech Support because the problem is "file specific" and not at the app level. I am not computer savvy and have never used a forum like this. Tech support just kind of dumped me here and said "have at it," so any guidance, help, etc. would be appreciated. I use Microsoft Office 365 as a personal/individual subscriber and my Access program started issuing error message over the past week. The biggest concern and problem is around db called Comic Books and I've attached the error message. When I click OK, it attempts to repair, fails and issues the second message. Another database--an earlier copy of Comic Books from mid December-- opens OK, but has its own problems, such as when I attempt to simply copy a table (see third error message). I don't know if these are related. Can anyone help me? Is there any hope for me ever regaining access to the Comic Books database which was last accessible and working on January 4? Thank you.
Access SQL Syntax Highlighting, Autocomplete, and Formatting
I just had Access (the newest version with Office 365) lose all syntax highlighting, autocomplete, and the formatting that had been allowed previously. It worked last night, and this morning it was all gone. The issue is on my Windows 10 desktop. It still highlights syntax and formats for readability on my Win 11 laptop. The only thing I can find between the two versions that is different is there is a checkbox for the Monaco query editor in Access on my laptop, but not my desktop. I would like to reiterate that it was fine last night on the desktop. I opened the same database this morning, and it was gone. I checked other databases, they all lack the highlighting and formatting on my desktop, but it is still there on my laptop. I attempted to update, repair, and reinstall office, and nothing changed. I am trying to determine what might have caused this, and if there is anything to do about it. The highlighting, autocomplete, and formatting are not a complete necessity, but they made working with the queries a lot easier for me, since I am a not particularly experienced with SQL.How do I reference query data from an Access Macro
I have a simple Select query that returns a number of records. In my Access macro (just for clarification, I do mean Access Macro and not VBA) I want to check how many records the query returns in an IF statement. In this specific case the check would be on zero returned records, but being able to check non-zero in the future might be useful. I have tried various internet searches but the only results I found relate to VBA. Suggestions on how to do this check would be appreciated. Thank You
Troubleshooting Queries in Access
Hi All, I am trying to run a query in an Access database, the query is expected to populate an existing table with new data, however it is not running as expected. As per the set-up process, 1. Have deleted old tables (with previous data), and imported new data for these tables from a different Access database 2. Then I am doing a compact and repair. 3. Then I am running query that is expected to populate the table, I see no records are added to the table Could this be a file reference issue **or** lack of data **or** missing tables /steps **or** a connection within Access. Appreciate step by step process to diagnose the issue
Query failure in Windows 11
Hi I just had a new computer at work, and changed from windows 10 to windows 11. I have a query, which compare 2 tables, and add rows in table2 that dont exits in table1. This has been working for years, but now it, only sometimes, double all the rows. INSERT INTO MPS Columns from Table2 (Access linked to sharepoint) SELECT MPS2. Columns from table1 FROM MPS2 WHERE not exists (Select 1 from MPS WHERE MPS.[MPSid] = MPS2.[MPSid]); It compares a unik field MPSid It doubles the rows sometimes, and the MPSid is the same, in the doubled rows Has something changed, or is there a workaround? Best Regards Tony
