How to make mousewheel work in VB6 IDE

idemousewheelvb6

One annoying behavior of the VB6 IDE editor, especially when switching back to it from more recent tools like VS.NET, is that it doesn't recognize the mousewheel! Maybe VB6 was brought out when most mice didn't have one, but is there a way to fix it so it does recognize the mousewheel?

Best Answer

Microsoft has an extension that can provide the behavior requested. You have to download it from the link below and register it with the steps provided, such as using regsvr32

http://download.microsoft.com/download/e/f/b/efb39198-7c59-4ace-a5c4-8f0f88e00d34/vb6mousewheel.exe

Update: Here are the steps

Download the VB6 Mouse Wheel.exe file that includes the add-in DLL and the code that is used to create the add-in DLL.
Extract the files to a location you have access to.
Open a command prompt, run as administrator.
Go to the folder you extracted the files to.
type regsvr32 VB6IDEMouseWheelAddin.dll, and then click OK
Start Visual Basic 6.0. Click Add-Ins, and then click Add-in Manager.
In the Add-in Manager list, click MouseWheel Fix.
Click to select the Loaded/Unloaded check box, and then click to select the Load on Startup check box.
Click OK.

Related Solutions

VB6 Editor changing case of variable names

Since I always find this thread first looking for a solution to messed-up casing, here is one Simon D proposed in a related question:

If you just need to fix one variable's casing (e.g. you accidentally made a cOrrectCAse variable and now they are all over the place), you can correct this for good by adding

#If False Then
    Dim CorrectCase
#End If

to the beginning of your module. If you save the project and remove the statement later, the casing remains correct.

Using Excel VBA I often accidentally change all Range.Row to Range.row by carelessly dimming a row variable inside some function - with the help of Simon D's solution I can fix this now.

Way to force the VB6 IDE to unload libraries

I've struggled with that for years back in the day, particularly when coding ActiveX DLLs for use with IIS sites.

The only real antidote I found was to keep the library loaded in a separate VB6 instance (assuming you have the control of the source). That way you could simply press the Stop button on the toolbar and the library would no longer be loaded.

Best Answer

Related Solutions

VB6 Editor changing case of variable names

Way to force the VB6 IDE to unload libraries

Related Topic