djiangr
asked on
What files do i need to run programs made in VB6?
I made program and sent it to someone else, and they sent it back telling me that they could not run it because of a missing file, but they weren't specific. I am pretty sure i read somewhere that you need some kind of "runtime files" to run programs in VB, if it was not installed on the computer already. could anyone tell me what is needed? thanks.
--and i can't really test on my compouter cuz it does run here.
thanks
--and i can't really test on my compouter cuz it does run here.
thanks
You can always install the VB Runtime Files in order to make your VB Compiled EXE to run in a pc.
You can download the VB Runtime Files at:
http://msdn.microsoft.com/vbasic/previous/2002/downloads/default.aspx
You can download the VB Runtime Files at:
http://msdn.microsoft.com/vbasic/previous/2002/downloads/default.aspx
if you have studio you can make an setup disk to install the program easily for your customer
ASKER
i installed the runtime files (i have a computer now that does NOT run the program, so i am using it to test what to get)
and it still doesn't work.
Run Time Error 339:
Component "COMDLG32.OCX" or one of its dependencies is not correctly registered: a file is missing or invalid."
and it still doesn't work.
Run Time Error 339:
Component "COMDLG32.OCX" or one of its dependencies is not correctly registered: a file is missing or invalid."
ASKER
i found the file on the internet and downloaded it, and then typed something into Start=>Run to register it.
but this seems to complicated to tell the people i need to give the program to, so how come the visual basic runtime files don't do this automatically? and how can i do this automatically?
but this seems to complicated to tell the people i need to give the program to, so how come the visual basic runtime files don't do this automatically? and how can i do this automatically?
Go to the Run item on the Start menu, and type:
regsvr32 <path & filename of dll or ocx>
regsvr32 <path & filename of dll or ocx>
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Always try to not using/ depending on ocx if possible, despite it's more easier to use and understand. Alternatively you can try replace the Common Dialog Component with pure APIs.
Example:
http://www.freevbcode.com/ShowCode.Asp?ID=631
'Package & Deployment Wizard' (PWD) is good for handling and creating an installer for VB compiled exe, alternatively you can also try this great free, more functionality to PDW and easy to use Install Packager, which is among the best for open source installer packager:
Inno Setup
http://www.innosetup.com
http://www.jrsoftware.org/isinfo.php
Example:
http://www.freevbcode.com/ShowCode.Asp?ID=631
'Package & Deployment Wizard' (PWD) is good for handling and creating an installer for VB compiled exe, alternatively you can also try this great free, more functionality to PDW and easy to use Install Packager, which is among the best for open source installer packager:
Inno Setup
http://www.innosetup.com
http://www.jrsoftware.org/isinfo.php
Hi,
To run a VB application, you need to register some dll's and ocx's. Actually these dll's may the controls you are using in a your form. The easiet way to solve the problem is to create a Package using the Package and Deployment Tool (Microsoft Visual Studio 6.0->Microsoft Visual Studio 6.0->Package and Deployment Wizard). Anyway you can also solve the problem either manually registering it using
regsvr32 "path" or doing it from your application itself. The code to register from application is
Shell(regsvr32 comdlg32.ocx /s)
Actually in this case the comdlg32.ocx should be in the same path as that of your application. Else you need to give the complete path. /s is used to suppress the message while registering the dll.
To run a VB application, you need to register some dll's and ocx's. Actually these dll's may the controls you are using in a your form. The easiet way to solve the problem is to create a Package using the Package and Deployment Tool (Microsoft Visual Studio 6.0->Microsoft Visual Studio 6.0->Package and Deployment Wizard). Anyway you can also solve the problem either manually registering it using
regsvr32 "path" or doing it from your application itself. The code to register from application is
Shell(regsvr32 comdlg32.ocx /s)
Actually in this case the comdlg32.ocx should be in the same path as that of your application. Else you need to give the complete path. /s is used to suppress the message while registering the dll.
For minimum requirements, which Not depends on other DLL/OCX, it needs MSVBVM60.DLL (Visual Basic 6.0 Run Times DLL) for VB 6 Compiled EXE, or MSVBVM50.DLL for VB5 Compiled EXE, and so on..