Hi !
Thank you very much for your response. Your second suggestion kind of helped. Whenever I delete the MOD files before a compilation run, the problem is gone. If I don't it remains.
About your first suggestion:
Do you still get the access violation when compiling without any kind of debug switch?
That was actually the first suggestion that I tried, though I'm not exactly sure what you mean. In the project properties under 'Compiler Options->Debugging' there was only one switch activated: 'Full checking code (/CHECKMATE)'. I deactivated that and tried again - with the same problem. (That was before I got to the point of deleting the MOD files)
If it gives any additional information on what the problem may be, here is what else I did before simply deleting the MOD files. It produced a rather weird result:
I had the idea to activate a few more of the flags to maybe show more compiler error messages, so I just activated all of the following flags: 'Debug information (/DEBUG)', 'Checking code (/CHECK)', 'Check for undefined variables (/UNDEF)', 'Full checking code (/CHECKMATE)', 'Full debug information (/FULL_DEBUG)', 'Array bounds checking (/BOUNDS_CHECK)' and 'Quick bounds checking (/QUICK_BOUNDS)'.
Then, instead of the access violation, it showed a couple of errors, but at locations where I hadn't modified any code since I'm working on the program. It simply said that arguments to a routine call were missing, when in fact the call seemed perfectly okay.
Moreover, when I deactivated any of the flags again, the access violation was back, regardless which flag I deactivated, even if it was one that was supposed to be included in another, like /CHECK in /CHECKMATE.
On one occasion, when the flag I deactivated again was 'Full debug information (/FULL_DEBUG)', I received a 'fatal error' instead of the access violation. However, when I tried to reproduce it, it was the original access violation again.
Well, at least now I have a workaround in deleting the MOD files before I compile.
Thanks so far for the help. 😃
Rainer