|
-
Aug 17th, 2000, 04:22 AM
#1
Thread Starter
Lively Member
Hi all!
I am using the following components and DLLs in my application; asycfilt.dll, comcat.dll, msvbvm60.dll, oleaut32.dll, olepro32.dll, shdocvw.dll, comdlg32.ocx, mscomctl.ocx, msinet.ocx, msmapi32.ocx, stdole2.tlb, tabctl32.ocx, and sysinfo.ocx. I use Installer Vise for compiling my setup package. In order to avoid version conflicts of shared DLLs I have set the installation folder as program directory. Removed their shared property. This was seeming to work OK. However, after I have installed some other application, my app did not start because of a version conflict on mscomctl.ocx. This means that my app is not registered to use the local mscomctl but the one on the system folder. Thus, when the system file is supersed than it bumps.. How can I avoid my app from malfunctioning because of these component updates? If local installation is a solution, how can I register these files to my desired location? Should I copy all external files to a folder and edit the project file references?
HEELP!!
Kiziltan Yuceil
Freelance Web/VB/VBA Programmer
"It's not what you know it's to whom you consult and with whom you collaborate"
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|