We have a VB6 Active X that is not registering 64bit Server 2008. RegSvr32 give me an error "The module ... failed to load" "Make sure the binary is stored ..." "The specified module could not be found." This appears to be a problem on any 64bit machine, but I was directed to post my question here. Thanks, -- Bill McCormick ACE-CO

As far as I know, All VB6 components are compatible under Windows 7. However, I cannot confirm if they are also with Windows 2008 x64. Is this a VB6 built-in component or something which was created internally?

It's something we have created internally. It registers for all Windows x86 OS's, but not x64, including server 2008. Thanks-- Bill McCormick ACE-CO

Hi, Visual Basic 6.0 runtime files are 32-bit. These files ship in 64-bit Windows Operating Systems referenced in the table below. 32-bit VB6 applications and components are supported in the WOW emulation environment only. 32-bit components must also be hosted in 32-bit application processes. The Visual Basic 6.0 IDE has never been offered in a native 64-bit version, nor has the 32-bit IDE been supported on 64-bit Windows. VB6 development on 64-bit Windows is not and will not be supported. For detailed information, please refer to the following article: http://msdn.microsoft.com/en-us/vbasic/ms788708 Tim Quan

Thanks Tim. So how to I get this thing to run in WOW emulation? Feel free to cut and paste your answer. Thanks,-- Bill McCormick ACE-CO

Hi, I suggest further discussing this issue in our Visual Basic forum: http://social.msdn.microsoft.com/Forums/en/category/visualbasic Tim Quan

OK. Which one? Most of them indicate that they are NOT for VB6 issues. Also, I'd like to point out that the first thing I did was to post a question to the "Where is the forum for ...?" forum and I was directed to post my question here. http://social.technet.microsoft.com/Forums/en-US/whatforum/thread/1223b116-092b-474a-be3c-c1a7be9eb123 I don't see a lot forum support for VB6 issues. Thanks, Bill-- Bill McCormick ACE-CO

The problem was a missing MSVBM50.DLL. Running a MSVBM50.EXE from MS fixed the problem. Thanks.-- Bill McCormick ACE-CO