David,

Thank you for explanation. I do a differnt approach on programming. I do all in classes. I have a strong application object that is reponsible for menu open database, version control window handling and the like. At least the global things are hooked to that. Since I can not rely on a simple database name, (Database is created by user at runtime from a meta construction) a form first have to figure out what database is opened. Information is stored on App. Object. I have global filters the form needs and stuff like that. And one of the first things the App object do is to check SYS(16) for VERINFO() it's needed for automated database update. I would need to programm a specialezed application object for that kind of testing (and to maintain). Since a compile need some 5 seconds normaly and 50s on REBUILD it might not be worth the trouble.

>While developing a form I test it by pushing the ! button on the toolbar in the designer.

I don't develop in forms - I do all in classes. Never pushed that button. (Actually it's removed from toolbar)

>While developing a block of code in a prg I highlight chunks of it and execute it to test, then move on to the next chunk. I keep doing this until it's all debugged, tested and running. Although this doesn't work too well in method code because this. references are not valid.

That's a big problem to me - I have two prg's the one is main and is standard (and well tested) the other holds some no vcx programmable classes like Header and Column - standard as well.

To test more simple constructions (this without object reference?) I have two makros to run highlighted block or complete edit window.

Conclusion
I have to think about it. Possibly I can trick my exe to load the classes out of vcx on disc instead of vcx on exe for development. The time I waste with my system is not the much in BUILD EXE, its more in Exe run and Database load (I waste a lot of time in integrity checks on load) as well adjustment of filters.
If I can hold the exe in memory and simple change the vcx beyond ... what a idea

Thank's for suggestions, this is worth a test <bg>

Agnes