Matt Pobursky wrote:

> 
> I've found that to be true with pretty much every tool set we use here.
> It's been our policy to archive the tool set used to create the production
> code at every release. It's the only way we can guarantee that we can re-
> create the code at a later date. We also put a note of which development
> tools and version were used to create the code in each header file for each
> module in a software project.
> 
> This strategy has paid dividends quite a few times. Just recently we had a
> client request a code change to a product that was designed by us back in
> the mid-1980's. We had the tools and code archived away and were able to do
> it, much to their surprise.

Here's a place where I'll get on my soapbox. Imagine for a moment if
your toolset requires a hardware dongle, key disk, or remote activation.
Can make it kind of difficult in some scenarios. I tried to explain that
recently to HiTech but they had themselves convinced that they weren't
going to lose any customers other than me.

Cheerful regards,

Bob
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist