>I think that my data files (dbf,scx,fpt) are overwriting the files that need replacing. I do use a post setup bat file to delete some old files hanging out in sub-directories that have been moved to newer locations. I didn't use the post setup bat file to overwrite any data files. It appears to be working correctly (the application). What about fxp's. Are compiled prg's overwritten?

I don't know - if they're handled on a datestamp check basis, then it's a matter of ensuring that the creation time/date on the new FXP is newer than the older FXP; there's no embedded file version detail to aid in the decision process. I know I've run into problems with direct updating of DBCs; fortunatley for me, SDT rebuilds them from metadata rather than relying on overwriting an existing DBC based on datestamp rules; before using SDT, I occasionally ran into problems where the DBC at the site had a more recent datestamp than the updated DBC sent out as a part of an update because of maintenance of the DBC on-site updating the datestamp detail. I'd guess that similar issues could exist with FXPs where on-site recompilation or file copies that did not preserve timestamp information had been done.