Sounds good to me, why don't you ask Rick.

>>In my server object I have taken those references out. Then on an install I keep a backup of that server prg and compare it (using something like Beyond Compare) to see what's new in the new server object, because I want to know what's new. Then I put anything new that's needed into my old server prg, not including pathes to thread, demo, etc.
>
>That's my point. I keep doing the same with the top level program.
>
>On an upgrade, even if all is documented, I am always afraid of missing a few adjustments like these. Wouldn't it be simplier if the upgrade could be done without affecting our code. I mean, the infrastructure could be done in a way that we could place our code at one place which will not be affected by an upgrade. For me, I have to put some code in wcdemomain.prg, which is the top level program, as I want to have some functions to be available all the time and not loaded each time. This is where I open all my tables, etc. Basically, a hook can do it. Or, is there such a think available?