Changes to class not showing up in .exe, but working when I DO *.prg

[JasonZ10]

Hi there,

I made some changes to an old class library on a piece of software that I work on, but I cannot get the changes to take effect in the compiled .exe. The changes do however show up when I run the program via 'DO main.prg' Does anyone have any idea why this might be happening? The project is under VSS version control and in VFP 9 SP2.

Things that I've tried:
Restarting everything (VFP/PC)
Ensured all file paths are correct and that I'm not running/using old files
Building with the "Recompile all" flag
Deleting all temp compiled files (FXP's)
Deleting the modified files and getting latest in VSS again, ensuring the changes are present
Running COMPILE CLASSLIB on the problem class

I'd appreciate any ideas of what else to try! The most puzzling thing to me is that running it via "DO main.prg" from within VFP shows the changes, but building the .exe out of that same .prg doesn't, and there are no errors when building.

Thanks!

 

[Mike Lewis]

My first thought on reading your question was that you should tick the "Recompile all" box when building the EXE. That nearly always solves this particular problem. But I see that you have already done that.

The only other thing that I can think of is that the VCX is read-only for some reason. Checking it out of version control should have made it read-writem but maybe it didn't do that for some reason. But it doesn't seem likely.

You might also try opening the VCX as a DBF (USE ...MyFile.VCX) and looking for a record whose Objcode field is not empty, then deleting the contents of that field.

All a bit of a long shot, I'm afraid. I hope someone else might have some better ideas.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads

 

[JasonZ10]

I appreciate all the suggestions, but no luck unfortunately. Is there anywhere else classes are cached perhaps? Or are compiled classes grabbed from somewhere outside of the project folder when the .exe is built? Any other ideas to try would be very much appreciated!

I'm assuming as an absolute last resort I could create a new project and compile from there, but that would not be ideal at all as I'd lose all VSS history.

Thanks