Visual Basic runtime DLLs and Controls When and how to install VB runtime DLLs, the OLE DLLs and the Common Controls and Common Dialogs Before you leave - Click the links to the left to investigate our software. Most of it is free. We hope that the information here will help you to solve two common problems: Compiled Visual Basic programs refuse to run, giving Unexpected error. The short answer: 1. Re-install the program which does not run. Many software installation programs supply the runtime program and controls they require. ( But ours do not so will probably not be fixed.) 2. Install the VB5 and VB6 runtimes to get the latest runtime and OLE DLLs. 3. Download and register the latest versions of the Common Controls. You cannot load a Visual Basic project into the IDE any more. The short answer: 1. Delete all the OCA files on your computer, VB will recreate them as needed. 2. Edit the project files to require Version 1.0 of all the controls. 3. If the errors include Licence not found, remove the common controls and reinstall VB. Please check all the items on this page. If the trouble is not resolved we are sorry, but we don't know what to do either. This page is kept up to date with everything we know. The VB authored Shareware and Freeware on this web site requires the VB5 runtime DLL msvbvm50.exe. Some programs may require the versions of Comctl32.ocx and Comdlg32.ocx supplied with VB6, but we are in the process of replacing them with versions that will run with the VB5sp3 controls. Now for the long answers. Getting programs written in Visual Basic to run To run programs written in VB you need to have on your computer the runtime DLL, a compatible set of OLE DLLs and a suitable versions of the required controls. To install them or repair an existing installation you should follow this sequence: If Windows is unable to run the program at all the VB.
Created a program in VB6 and compiled it. It goes through it's Copying Files then says some files are out of date and I need to restart to update the files. I'm guessing that it has to reboot so it can register these DLL's. But when I reboot, it copies the same files again and prompts me for the same reboot every time. I resolved this problem before by writing a program to register these DLL's. This was a very painstaking process to run this program on each client install. Now we have a need to deploy this program at remote sites and I will not be there to provide the TLC this registration process requires so I really need to resolve this issue once and for all. I've discovered that the DLL's are stored in this directory prior to reboot: Cocuments and Settings MShea.000 Local Settings Tempmsftqws.pdw The files are as follows: MSJET40. DLL EXPSRV. DLL MSJTES40. DLL MSRD2 X40. DLL MSREPL40. DLL MSVCRT. DLL The SETUP. LST contents are as follows: [ Bootstrap] Setup Title= Install Setup Text= Copying Files, please stand by. Cab File= Road Map. CAB Spawn= Setup1.exe Uninstal=st6unst.exe Tmp Dir=msftqws.pdw Cabs=1 [ Bootstrap Files] File1=@ VB6 STKIT. DLL,$( Win Sys Path Sys File AM,101888, File2=@ COMCAT. DLL,$( Win Sys Path Sys File $( DLLSelf Re gister AM,22288, File3=@ STDOLE2. TLB,$( Win Sys Path Sys File $( TLBRegis ter AM,17920, File4=@ ASYCFILT. DLL,$( Win Sys Path Sys File AM,147728, File5=@ OLEPRO32. DLL,$( Win Sys Path Sys File $( DLLSelf Register AM,164112, File6=@ OLEAUT32. DLL,$( Win Sys Path Sys File $( DLLSelf Register AM,598288, File7=@msvbvm60.dll,$( Win Sys Path Sys File $( DLLSelf Register AM,1388544, [ Icon Groups] Group0= Road Map 3.0 Private Group0=-1 Parent0=$( Programs) [ Road Map 3.0] Icon1= Road Map.exe Title1= Road Map 3.0.
Download Now