From: Ray Bay (raybay_at_cia-g.com)
Date: Tue Mar 02 1999 - 09:38:31 EST
The general rule is, "If it isn't broke, don't fix it."
When you have an older file that has been working for you,
don't change it unless you have a very good reason. There
are hundreds of instances where the newer file causes damage
or problems that were unknow under the older file.
Go to www.microsoft.com and research the knowledge bases. Go
to other sites on the web. You can usually find details that
explain why you need to use the newer or the older file.
I have had large numbers of clients who have paid me good money
to fix things they screwed up with these updates... One of the most
common being, "...unable to find _____.dll..." or unable to find
another key file or element after doing these replacments...
If you KNOW why you are replacing, you are pretty safe. If you are
replace just because it is a more recent release, and your software
packages are old ones, you could be causing yourself a late night
at the keyboard.
This archive was generated by hypermail 2.1.3 : Thu Jan 23 2003 - 09:54:47 EST