"mayayana"  wrote in message
news:Ywkvc.8782$Yd3.7448{at}newsread3.news.atl.earthlink.net...
snip... >
>      I wonder if I.S. might have an option to package older files
> and NEVER overwrite a file with same or later version, similar
> to the PDW Redist folder? That seems like a better
> approach to me because you can still ship, say, OLEAUT32.DLL
> in case a Win95 or NT4 system needs it, shipping only the
> latest version necessary, and without worrying about problems
> delivering it to Win2000/XP since it won't get installed there anyway.
>
snip...

Yes, that was what I was asking about or suggesting. There are several
options in InstallShield to deal with installing 'companion' files (my
wording). Yoiu can select "always overwrite', 'only overwrite older
versions', 'never overwrite' and more.

If  I select 'never overwrite' it will install OLEAUT32.DLL (and others) if
not already present, but will not overwrite if a copy is already there.

I'm quite confident that would not mess up the target machine, but I wonder
if my application, developed/debugged with the 'current' DLL, will opertate
properly with the old DLL.

Bob
---
þ RIMEGate(tm)/RGXPost V1.14 at BBSWORLD * Info{at}bbsworld.com

---
 * RIMEGate(tm)V10.2áÿ* RelayNet(tm) NNTP Gateway * MoonDog BBS
 * RgateImp.MoonDog.BBS at 6/2/04 5:03:59 PM