Thanks Nadia and Irv for trying to help.

I realize now, after solving the problem, that I omitted an essential detail in describing the situation.
The “detail” was that we run the launcher program, compiled as .exe every time we start VFP. It is the same .exe that runs on production machines, and we run it in development only to have the environment set to a our custom configuration.
What happens is that all classes used in an exe (class libraries included) are loaded in memory, and NOT CLEARED when the exe exits. As a result, more recent changes made to classes are not seen, if an exe built before changes is run.

I found two ways to get rid of the old classes in memory:
- open the class - not practical, you have to do it manually
- use CLEAR CLASS classname - I have that in code, use avcxclasses() on all our class libraries - this seems overkill, but it works...

I have to say that I don’t find a good reason that the class is left in the memory after the exe exits, and that there is no way to check what classes are in memory (or is it?).