I have created a simple stock control system using VB 6 & Access 2000. The created system works fine on my PC but if I try it on another Win 98 PC not running VB6 or Access it will not run. I have heard I need to include something for it to work. Does anyone please know what this "something" is & how do I go about doing it? Also if I were to run this stock control software on a PC running XP would it work without making any changes? Thanking you. Regards M

You need to run the setup and distribution wizard that comes with VB6. This will create the necessary CAB files that will contain all the files you need to run the programme on a system without VB6 or Access. Any VB6 application, and especially one using data access, is going to need a lot of runtime files, DLLs mostly. The setup and distribution wizard does a pretty good job of identifying them for you. Stuart

Thanks Stuart, I knew there was something. I have actually got so far with the wizard but became confused at some point and did not bother as for that project all PCs were "developer PCs" and had the software installed. As the target PC for this project does not and is running XP Home do I still have to run the wizard for it to run with XP? Regards M

You will have to run the Wizard and the use the resulting distribution package on the target machine. You can use some other Windows Installer which will do the same job, but you already have the Setup wizard with VB6. The distribution package will contain Setup.exe, setup.ini and one or more CAB files. During the process you will be asked if you want to create multiple CAB files, or one huge single CAB file. Go for the multiple option. The single CAB file tends to be a bit slow during the installation process. If you run the Wizard on a Win XP machine, you may have problems running the application on a Win 98. Some of the DLLs are incompatible between platforms. It entirely dependant on what functions and procedures you application use. You can get round this by making two different distribution packages, one on an XP machine and one on a 98 machine. Stuart

You need some runtime DLLs such as msvbvm60.dll, oleaut32.dll, olepro32.dll for VB6 to run on PCs which doesn't has VB6 installed (client's PCs). There are some sites provide you an installing package of VB6 runtime dlls, download it and install it on the PCs that runs your project. You can download here: http://www.moochers.com/index.html?w95files.html (the last one in the list) Notice that if you have VB SP4 or SP5 installed on your PCs, then you have to find out the VB6SP4 or VB6SP5 runtime DLLs; go to www.google.com and search for [b]VB6 SP4 Runtime dlls download [/b] If you have a database project, then you need to install mdac( Microsoft Data Access Control) library and also Microsoft Jet 4.0 engine on the PCs. You can download mdac and Jet 4.0 here: http://www.softaura.com/unic/download.asp The site above supports you mdac 2.6, if you have another version of mdac you need to download the suitable version. For example, if you need mdac 2.8 then go to www.google.com and search for [b]mdac 2.8 download[/b] If you used MS Form 2.0 controls in your project, then for the PCs which doesn't have MS Office installed, you need MS Form 2.0 dll. Find the file fm20.dll in your PC's system folder (C:\Windows\system32 if you are in XP; C:\WinNT\system32 if you are in Win2k; and C:\Windows\system if you are in Win9x). Then copy the file and paste it to the system folder of your client's PCs, after that, register it with regsvr32 at the DOS command prompt with the syntax like this: [b]regsvr32 fm20.dll[/b] Remember that if you used some third party's DLLs or OCXs, then you need to copy, paste and register them with the client's PCs Last note: instead of install the needed files seperately like what above, you can make a setup package for your project including all above needed files, then just install your application on the client's PCs

>> Last note: instead of install the needed files seperately like what above, you can make a setup package for your project including all above needed files, then just install your application on the client's PCs<< Brilliant tuantt! Thats exactly what the Package and Deploymant Wizard does as described above; with not having to worry about which version of VB6 you have which, what other DLL's you nedd or what third party OCXs you need to install. THE P&D Wizard does it all - automatically Stuart