Hi all,

I have a "wierd" situation (aren't they all) where a programmatic class goes "missing" after returning from the FoxFire report writer. That is, it is a fairly common class that is created programmatically in one of my procedure files. So at app startup, SET PROCEDURE is fired for this .prg which contains that class and some subclasses. This app is bunded into a .exe. This never seems to fail until...

The user goes into the FoxFire report writer (Foxfire.app) and when the user exits, the next time this class is required, an error is thrown saying the class is not found. But looking through the captured details, the procedure file is still in the procedures list and so are all the other loaded .vcx classes.

I tried issuing SET PROCEDURE TO MkProcs.prg again but that did not help. I tried clearing the specific class with CLEAR CLASS cusParamObject and then re-issuing SET PROCEDURE but that did not help. Since it only seemed to be a few of the programmatic classes that were effected, I eventually worked around this by moving them into a .vcx as a visual class. That seems to have solved it but I am not really sure it is a "fix" - and the classes were small enough that I would have preferred to leave them programmatic.

Any ideas?
Thanks,
Albert