I am trying to restore mouse wheel functions into the VB6 IDE. The microsoft-supplied dll will not register giving the error code 0x80004005. This is supposed to be a previledge-related error. UAC is off. Command prompt runs with administrator previledges. Anybody know how to get around this? Thanks

Hi, Thanks for posting in Microsoft TechNet forums. I recommend you do the following: 1. Run CMD.exe as administrator 2. Browse to SysWow64 folder 3. Use normal REGSVR32 command for registering the VB6IDEMouseWheelAddin.dll 4. Go to Add-in manager in VB6 IDE & add Mouse Wheel in normal way. Hope it helps! Best Regards, Miya Yao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comThis posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thank you for the reply, Miya. Regrettably it did not work. I received the same error.M Whipps

The above issue occurs when you try to use a fully qualified domain name (FQDN) to connect to the Microsoft Office Project Server 2003 Web site. To resolve this issue, use one of the following methods: * Use a host name, such as: http://projsvr2003/ProjectServer to connect to the Project Server Web site. * Use the WinHTTP Default Proxy Configuration Tool to add the FQDN to the Bypass List. To add the FQDN to the Bypass List, follow these steps: 1. Click Start, click Run, type cmd, and then click OK. 2. Type the following command line, and then press ENTER: Proxycfg -d -p * "<local>;servername of WSS;FQDN of WSS;ipaddress of WSS" 3. At the command prompt, type iisreset and then press ENTER. The iisreset command stops and then restarts Microsoft Internet Information Services (IIS).

Hi, Please refer to this KB http://support.microsoft.com/kb/837910 , follow the methods there to see if it works. Regards, Miya TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comThis posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hello, Thanks but I have already tried that. The VB project won't load because it is missing "connect.dsr". M Whipps

Thanks for answering, Kristain. I'm not using Project Server.M Whipps

Since the Visual Basic 6 is out of support now, I recommend you upgrade the software, it could resolve the problems. If you have any other windows questions, we are glad to provide any help. Regards, Miya TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comThis posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Really?!? Suggesting that a developer change his environment because a mouse won't scroll is like telling him to cut off his foot because he has poo on his shoe. It is common knowlege that the VB6 to .NET conversion routines simply don't work for any but the most trivial of solutions. Thanks anyway.M Whipps

I suggest you also ask this question in MSDN forum, since we couldn’t provide more information here, you can get some help in that forum. Thanks for your understanding. Regards, MiyaThis posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi. The difference for Win 7 is that you need to copy the file to: C:\Program Files (x86)\Microsoft Visual Studio\VB98 The rest of the process is the same... Regards, Nelson - from Brazil.

Thanks Nelson. That didn't work either. Same error code.M Whipps

This worked for me: Copy VB6IDEMouseWheelAddin.dll to C:\ Run Command Prompt at administrator (right click on Command Prompt and choose Run As Administrator option) Run C:\Windows\System32\RegSvr32.exe C:\VB6IDEMouseWheelAddin.dll Open VB6 Open Add In Manager and select MouseFix from list Check Loaded\Unloaded Box and Load on Startup Box You Mouse Wheel should now work! :-) NOTE: I was not able to get this to work with VB6IDEMouseWheelAddin.dll in any other directory but root! NOTE to MS staff: There is still a LOT of legacy VB6 code out there that companies hav not migrated to .NET. Telling us to not use VB6 or other VS6 development tools in newer Operation Systems is just pissing off your previously loyal developer community. Please remember how you got so big to begin with! thanks, Steve

This worked for me: Copy VB6IDEMouseWheelAddin.dll to C:\ Run Command Prompt at administrator (right click on Command Prompt and choose Run As Administrator option) Run C:\Windows\System32\RegSvr32.exe C:\VB6IDEMouseWheelAddin.dll Open VB6 Open Add In Manager and select MouseFix from list Check Loaded\Unloaded Box and Load on Startup Box You Mouse Wheel should now work! :-) NOTE: I was not able to get this to work with VB6IDEMouseWheelAddin.dll in any other directory but root! NOTE to MS staff: There is still a LOT of legacy VB6 code out there that companies hav not migrated to .NET. Telling us to not use VB6 or other VS6 development tools in newer Operation Systems is just pissing off your previously loyal developer community. Please remember how you got so big to begin with! thanks, Steve Thank you Steve. That didn't work either, I'm afraid. I still get the same error code. I really must agree with your comments about VB6. I have over a half-million lines of code in production currently and there's no way I am prepared to rewrite it all, or to pay a conversion company $20,000 or so to have them attempt to convert it. And that's not even taking into account the .NET hell you get involved in. I don't really understand why MS wants to just throw us to the dogs. I do see and value what .NET exposes but the paradym shift from procedural to object - oriented code which may be worthwhile for C, and C++ coders is a huge PITA for my team. Plus, the keyboarding load is ridiculous! MurrayM Whipps