>Once again, thanks, but still no go. My TRY/CATCH still reports that the code is in use, and can not erase the FPX.
>I have arrived at a means, but it is kind of dirty. I am erasing all the FPX in the Temp folder. If any leftover, they are removed.

I think you were hit by a garbage truck. Fox will keep all libs (vcx and fpx) open as long as there's a reference somewhere in memory, and perhaps you're just too fast, i.e. between clear class etc and erase command there isn't enough time for the references to clear. We don't really know when they do, perhaps when the routine exits, or you may need to call some obscure sys() function, dunno.

I've seen this done with vcxes - just a couple of records per class - where the generated code goes into the .methods field and then you compile class. This recompiles the whole lib, but then this was used with a limited set of classes, perhaps a dozen per classlib, and it has to create the records only once per session, so the speed wasn't an issue.

For prg classes, sys(2015) was my friend when I had to do this - and these would go into %temp%, where I erase everything older than 3 days on quit. So I wasn't even trying to delete the .fxp while it's fresh.