Random errors: what can cause them

Display in a destructor:
Don't ever try to display anything in a class destructor, at least in WinDev 5.5... Any Info(), trace(), YesNo() or other display instruction will cause an error message "forbidden instruction" during the execution of the program (nothing during compilation, of course).. And that's when you are lucky...

In some cases, and I regret to say that I was not able to identify exactly when, you will get a GPF instead. And of course, nothing will tell you where the error is coming from. Don't forget, in case of reproducible GPF, to always execute your program in test mode to try to get more information on the problem. Of course, the behavior is often different in that case, but it's always the first thing to do.

In WinDev 10, displaying information in a a class destructor doesn't seem to create a problem.