How about compiling with the intervening releases ie Build 13505 and Build 13622 and see what happens?
Then you could hopefully narrow it down to a particular build and the release notes may give some clues.
v13622 release notes mention two new features that I am guess are candidates for new troubles - ASLR, DEP. Unfortunately, not the easiest to sort out for testing as these are project file settings AND the program involves 30+ dlls.
For anyone interested, this problem can easily be replicated in the School example program. A PTSS has been filed, but I suspect there may be other instances where the problem can pop-up in post v13622 apps.
Carl - Thank you. Helpful to know as it does give me some hope. I will take some time to reconsider 20+ year old code to avoid using an array.
It’s always discouraging to invest a load of time in tracking down a SV bug, create a PTSS, and then never see that the PTSS has ever been opened for review. Even when eventually fixed, just knowing someone has actually considered the issue after being reported would be nice.
Define a local group and declare the array is over the group.
Use the group in the browse list.
This looks to avoid the GPF caused by using the array itself in the list.