Forum Discussion
Office v2508 feature update (new vbe7.dll) breaks library compatibility with LTSC VL versions
I can reproduce the issue in v2507 and have just reported it to the Access team.
In fact you don't need to use the 2508+ ACCDE as a library file to trigger the error. It also occurs if you try to run the code directly from the ACCDE in 2507
As you say, it isn't clear whether this is a bug or by design. However when the move of RegEx to the VBA library was done in 2508, the documentation clearly stated that it was planned to not cause compatibility issues.
First of all: Thank you for reproducing and forwarding the issue!
That's interesting: So far, I have not been able to reliably reproduce the issue with just the accde alone. What I tried was to (a) add a ShowColorCode method that shows the value of vbRed in a MsgBox, (b) add an AutoExec macro that calls ShowColorCode and (c) run the accde on 2507-. How did you manage to repro the issue with just the accde alone?
(This issue strongly reminds me of the ADO Windows 7 SP1 problem. Apparently, making changes to COM libraries without breaking binary compatibility is not an easy task.)
I just opened the ACCDE file directly in v2507 and ran GetColorCode from the immediate window. That triggered the error
Offhand, I can't remember the ADO Windows 7 SP1 problem you mentioned. I do remember a major issue with queries in 2003 SP3 that required a hotfix.
I also found this MS support article from 2022 on a similar issue with ACCDE files which was rapidly fixed: Error when trying to open an ACCDE/MDE file created in a different version of Access - Microsoft Support
Ah, yes, calling GetColorCode from the immediate window also triggers the problem. Thanks, that simplifies the repro.
(The historic ADO incident I remarked on was a similar situation, where VBA & VB6 applications that used ADO and were compiled on Windows 7 SP1 did not run on PCs with Windows 7 without SP1 or older operating systems. There was an interesting blog article about it on "http://blogs.msdn.com/b/psssql/archive/2011/10/03/yes-we-made-a-mistake-and-are-finally-going-to-fix-it.aspx", but since all those old MSDN links broke some years ago, it can only be accessed through Internet Archive (which is down right now) nowadays.)
