Applies to: Palisade software used with Excel, releases 5.x–7.x
Does Palisade software use Visual Basic? How do I install that on my computer?
There are actually two things called Visual Basic: Visual Basic for Applications, which is part of Microsoft Office, and the Visual Basic 6 Runtime, which is part of Windows. Both are needed for most Palisade software; this article is about the Visual Basic 6 Runtime.
In a normal installation of Windows and Office, this is already present and there is no need to install it. This article tells you how to verify that you have it, and what to do if you don't.
All Palisade products except the Palisade Custom Runtime use the Visual Basic 6 Runtime—also known as the Visual Basic 6 Redistributable or Redistribution Pack—which has been part of Windows since Windows XP. The main file for the VB6 Runtime is MSVBVM60.DLL, located in C:\Windows\System32, C:\Windows\SysWOW64, or both. Use Method 1 or Method 2 to verify the file.
Method 1 (recommended):
Open an administrative command prompt. You must run this procedure in an administrative command prompt; even if you have administrative privileges, you cannot run this successfully via a Start » Run window.
Download the attached KB1490_Reregister_MSVBVM60.bat file to a convenient location—save it, don't run it.
Shift-right-click the downloaded file and select "Copy as Path".
Click into the administrative command window. Right-click and select Paste, then press the Enter key.
Notice two things: the version number displayed in the command window should be 6.0.98.15 or greater, and the pop-up message should be "DllRegisterServer ... succeeded". If either of these doesn't happen, follow the instructions in the command window.
Method 2:
In File Explorer, locate the file and select Properties. On the Details tab, check the file version and verify that it is at least 6.0.9802 (for Windows XP) or 6.0.9815 (for Windows 7 through Windows 10). If it is outdated, download and install the latest. As of this writing (2017-10-23), the latest version is Service Pack 6, which was released in 2004. It's available at https://www.microsoft.com/en-us/download/details.aspx?id=50722.
If it's up to date, but you're having a problem that referred you to this article, re-register it with the following steps.
Open an administrative command prompt. You must run this procedure in an administrative command prompt; even if you have administrative privileges, you cannot run this successfully via a Start » Run window.
Enter one of these commands, depending on the actual location where you found MSVBVM60.DLL, and press Enter:
regsvr32 C:\Windows\SysWOW64\msvbvm60.dll
regsvr32 C:\Windows\System32\msvbvm60.dll
It's okay if the file is not in both locations, as long as it's in at least one of them.
You should get the response "DllRegisterServer in C:\Windows\SysWow64\msvbvm60.dll succeeded" or "DllRegisterServer in C:\Windows\System32\msvbvm60.dll succeeded".
If the regsvr32 command responds with "The module ... was loaded but the call to DllRegisterServer failed with error code 0x800a0046" please repeat steps 2 and 3 but this time open an administrative command prompt.
If the regsvr32 command gives any other response, please send a screen shot to Palisade Technical Support with your serial number, a reference to this article, and details of your original issue.