dll's needed to run a VB .exe?

[BadgerFan]

If I have created an executable and want to move it to another machine to run it on, but dont want to perform an install of VB on the machine, what dll's do I need to move to the other machine? Is this even possible. I was thinking that maybe there were some run time dll's that I could just move.

 

[sdb510]

My company has a special build we install on machines that need to have a VB app or an app that uses Crystal Reports installed on it. This way, only the application-specific files and reports can be distributed without needing the runtime files packaged along with them. Here is a listing of the files we use:

General VB32 runtime support components
-----------------------------------------
Mfc42.dll
Comct332.ocx
Comctl32.ocx
Ctl3d32.dll
dbgrid32.ocx
Grid32.ocx
Richtx32.ocx
Dblist32.ocx
Mscomct2.ocx
Msacal70.ocx
Msflxgrd.ocx
Msmask32.ocx
Msstdfmt.dll
Tabctl32.ocx
threed32.ocx
Mshflxgd.srg
Mshflxgd.ocx
Mshflxgd.oca
Mshflxgd.dep
Grdkrn32.dll
Olemsg32.dll

File installations for Visual Basic V5.0
------------------------------------------
MSVBVM50.dll
ComDlg32.ocx
comct232.ocx
Stdole2.tlb
Oleaut32.dll
Olepro32.dll
Asycfilt.dll
ComCat.dll

File installations for Visual Basic V6.0
----------------------------------------
Advpack.dll
msvbvm60.dll
scrrun.dll
MSCOMCTL.OCX

ODBC JetdB components for VB-32
-------------------------------
Msjter35.dll
Msjint35.dll
Msjet35.dll
MSJTER32.DLL
MSJINT32.DLL
Vbajet32.dll
Vb5db.dll
MSRD2X32.DLL
Msrd2x35.dll
Msrepl35.dll
Odbcjt32.dll
Odbcji32.dll
Odbctl32.dll

Windows Data Access Objects for VB-32
--------------------------------------
DAO350.DLL
Dao2535.tlb
DAO2532.TLB
DAO3032.DLL

Microsoft Distributed Transaction Coordinators for ODBC DB
----------------------------------------------------------
Msrdo20.dll
Rdocurs.dll
Adme.dll
Dtccm.dll
Dtctrace.dll
Dtcutil.dll
Msdtcprx.dll
Xolehlp.dll

I know this is a lot of files, but I'm not sure what kind of system you are running. Hope this helps.

Steve

 

[Antzz]

Well, just copying will not help. You need to register the dlls too on the destination machine. And with so many files around you will surely miss a couple.

The files mentioned above are usually not used all the time. sdb510 has listed all the object components (which I am sure that you are not using all).

So you need to know what files you are using and then copy and register them on your machine.