Step by step tutorial on how to create a VB application that integrates the. Integrate the Licensing Library within application; 7. Done - Build and install; 8. You will not be able to test the application until you install the MSI package.

InstallShield Express is a leading Windows installation development solution. It is designed to enable development teams to be more agile, collaborative and flexible when building reliable InstallScript and Windows Installer (MSI) installations for PCs, servers, Web and virtual applications. InstallShield Express can directly convert MSIs to Microsoft App-V virtual packages and includes automated tools to productize, install and bundle software in application virtualization and traditional EXE and MSI formats.

I'm not absolutely sure about the answer to this question but I would like to follow this thread myself. I believe that the answer has something to do with downloading the latest drivers for your operating system. Possibly updating to the latest service pack for your OS. Thank you for asking this question, because I believe that we all need to know the answer to this.

Is it possible that we might have to compile our apps in every OS environment individually? That is what I think must ultimately be done. I will be following your thread with great expectations. I have had my vb6 programs work on all versions of Windows. I have compiled on XP 32bit, Vista 32bit and now I compile on Windows 8 64bit. A few years ago I decided to add some functions that were not available for Windows 2000 but that is not important now since it works on XP, Vista, 7 and 8 (even on starter versions) all of these on 32 or 64 bit variants.

There were some cases where initially my programs would not work and here is what I did. 1) For Windows Vista, 7 and 8 you need to Run as Administrator You may need to change advanced properties every time you reinstall. 2) In some cases you also need to install a VB6 Runtime update downloaded from Microsoft?s website 3) Less likely you need to install some dlls and ocxs yourself like MSCOMCTL.OCX That's all I could remember for now. I'm sure Rob Crombie will jump in at some point, bemoaning the issue of dependencies of your run-time and creating apps that are independent of other components, but the bottom line is that it happens. (Sorry Rob to spoil your thunder:-) As most people have said, there shouldn't be an issue if you follow the guide lines. Jorgearr's list is pretty good, but you also need to ensure that you: a) Use up-to-date database technologies as there are problems with trying to installing legacy DLLs on system that already have a newer version installed.

It's the 'I've got a later version already, I'm not going to install that older version' symptom. B) Use a 'sensible' installer that understands about dependencies and COTS type OCX dependencies such as ADO drivers etc. Then, it's a matter of testing on various clean machines.

Using a virtual machine is good for that. As Rob Lee's implied - is there anything wrong at the moment?

Chasing an invisible problem will waste a lot of time. It has to be said that VB6 isn't fully compatible with Windows Vista and Windows 7 any other statement would be misleading. I have had a lot of problems with my Old VB6 App and immediately switched to C Sharp the learning curve was rather tiring though, but now I am very comfortable. Some of the issues I have had with my old VB6 app in Windows Vista and Windows 7 is sockets communication, I think this is due to hardened security in Vista and Win 7. Chertezhi torgovih centrov. VB Apps seem not to work well. My Notify Icon on System Tray used to hang in Windows 7 and vista even when I exit the app but works well in Windows XP. A friend of mine had issues installing VB6 IDE on Windows 8 that's when I learned that The Visual Basic 6.0 IDE is no longer supported as of April 8, 2008 by MS.