Distrubuting VB APP w/o registering OCX & DLL 1

[BlindPete]

All right hotshots,

I have a client whose MIS guy hates MS. They do not want us to register any DLL's or OCX for fear it will mess with other legacy VB5 componants they desire to not update.

Is it as simply as including the VB DLLs ands whatever OCX's I use at the same location as the EXE?

Any insight would be greatly appreciated.
-Pete

 

[Ruairi]

no, it's not. necessary dll's have to be registered or the app will not work. Ruairi

Could your manufacturing facility benefit from real time process monitoring? Would you like your employees to be able to see up to the minute goal and actual production?
For innovative, low cost solutions check out my website.

http://www.plccontroltechnologies.com

 

[jmarler]

Pete,
If you are currently designing an app for someone and they do not want all of the COM installations, then perhaps you should consider designing a web app for them. This way, the client machine would only need to have a web browser and the COM installation would be limited to a small set of machines (IIS/MTS). Just a thought . . . B-) - Jeff Marler

http://www.JeffMarler.com

(please note, that the page is under construction)

 

[BlindPete]

Unfortunately I am a victim of sales/marketting forgetting to pass along this tid-bit. They figured it was minor issue. Had I known this we would have selected Java or VFP over VB for this dirt simple application.:-(
-Pete

 

[JohnYingling]

If the OS is Win '98 second edition, ME or 2000 then there is an option for installing different versions of DLLS "side by side". See

http://msdn.microsoft.com/library/techart/sidebyside.htm

http://WWW.VBCompare.Com