>>In my application I distribute, I have added a few OCXs. Now, for those required files that the OCXs are using, I have a situation where I have multiple versions of the same file.
>>
>>For example, I have MSVCRT.DLL, MSVCRT20.DLL and MSVCRT40.DLL. If I only include MSVCRT40.DLL, will that do it? Or, should I keep them all?
>Michel,
>Unless the intended machine(s) have lack of storage space problem, I strongly recommend including ALL necessary OCXs, DLLs, etc., even if you have to distribute multiple versions. This will help you and your client tremendously by greatly limiting future compatibility problems.
>
>On a similar subject, I've always had a problem with every version of Windows (including 3.1, 95, etc...) and most of my and my clients problems ultimately is related to some shared DLL files that went awry. Sharing DLLs, IMHO, is a BAD systems architecture. The concept of sharing a library compoent to save space, memory, etc. is understandable and maybe even desireable but in reality, it usually turns out to be counter productive at best. How many times have you installed a software that overwrites a different verion of the DLL (whether it be coincidental same name or just an older version) and other programs start to crash and bring the system down??? I could go on and on but...
>
>I apologize for rambling on about your simple dilema but I think I made my point pretty clear :))))

I'll keep them all. I found that those files are not necessary new versions.