Issues with VBA after upgrading to Version 2311 (Build 17029.20108)

Anonymous
2023-12-18T11:06:31+00:00

Hi, after updating to Version 2311 (Build 17029.20108), we face seriously many issues with our Excel Macro solutions. Something we have never seen before (or at least not for a long period of time). Even things like standard commands like thisworkbook fail. We had to change to 'Monthly Enterprise Channel 2310', which fixed the issue.

Also, it happens on different computers, with different workbooks, so it's not a question about reinstall Excel or something like that.

Btw. We have been working with Macros as our Core business for more than 8 years, and have millions of lines of code. So we normally know what we do.

Is there other people in here which get the same kind of errors with VBA using this version?

Microsoft 365 and Office | Excel | For business | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2024-01-10T18:50:07+00:00

All our issue was fixed by rolling back from Version 2311 (Build 17029.20108) to Version 2310 (Build 16924.20180).

We had all kind of weird issue with this Version 2311 (Build 17029.20108).

Was this answer helpful?

6 people found this answer helpful.
0 comments

157 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-02-13T06:33:37+00:00

    I have similar problems with Word 365.

    So far i have identified two problems in a set of macros that have worked OK for years.

    1. Extracting the chapters from book-file failed after five-eight chapters. No problems on a fast PC. Problem traced to a timing issue when writing the extracted chapter to disk. Solved by introducing a 0.5 delay before the instruction. (Already when creating the macro, I found it necessary to insert a delay here, but then 0.2 sec was enough.)

    2, Earlier the extracted chapters had the same custom margins used in the original file. Recently that changed to the copies having the default Word margins.

    Fixed that by adding routines setting the copies to the original's margins.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-02-13T07:35:40+00:00

    Have you had the issue where the VBA simply doesn't execute and even crashes Office?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-02-13T09:05:00+00:00

    I have some routines that don't always execute properly, but I'm not prepared yet to blame VBA for that. I have had no office crashes.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-02-13T10:01:05+00:00

    Yes, in this version of Excel, the quick fix is to move the file to an untrusted folder, so macros are not enabled in the first place. Before enabling the macros, you need to press F11 and compile the VBA project. Then, save the file and open it again in a folder that is trusted. This fixes the bugs in many cases but only for a period of time.

    Was this answer helpful?

    0 comments