Need help getting VBA working on new computer

Hi guys. I am a technician who is trying to comply with the IT mandatory Win7 computer upgrade.

I have some test systems that were written in VBA that are being problematic. I was able to figure out how to get the bad references fixed, but the program still is not working correctly. I can now start the program, but the first thing it does is have the user select the COM port. COM1 is available according to the Windows Hardware Manager. However, the buttons that allow the operator to select the COM ports are all grayed out (Excel does not recognize that any ports are good to use.) Does anyone have ideas how to get this running? One of the things I tried doing is copying the old reference files from the other system and relinking them, but that did not work at all. Does anyone know how to get an old reference working? (E.g. the original system uses "Microsoft Excel 9.0 Object Library" and the new system uses "Microsoft Excel 14.0 Object Library")

I am competent in C++ coding, but VBA is completely new to me. Any advice you guys can offer would be much appreciated.

Unfortunately, I wouldn't be able to trust myself to be able to remove confidential information from that much code. I'm still not sure how deep it goes due to the fact that I didn't even know one could program in Excel until just last week.

Is there anything I can search for that would indicate what is getting the COM port info?

I was able to find this:

Please Login or Register  to view this content.

Edit: This does look much better.

The .channel thing is being thrown around quite a bit. I found some more stuff pertaining to the serial port:

Please Login or Register  to view this content.

I also pulled the references here:
Visual Basic For Applications
Microsoft Excel 9.0 (now 14.0)
OLE Automation
Microsoft Office 11.0 Object Library (now 14.0)
Microsoft Forms 2.0 Object Library
X328CommX ActiveX Control module (pulled from previous system)
CCRP High Performance Timer Objects [VB6] (pulled from previous system)
Microsoft Scripting Runtime


"Microsoft Excel 9.0 (now 14.0)" This means that the original system was running Excel 9, but the new system is running 14.

Does this help any? (And thanks for spending the time to help a noob out.)

When I say "Pulled from the previous system" that means that I found the DLLs (and other files) that were being called on the old system and copied them to the new system in the same directories.

Thanks for trying. I am currently trying to go through tutorials (the ribbon that MS Office uses now invalidated most of the decent looking tutorials I have found so far). I am also looking in rewriting all of the COM port stuff from scratch using a different driver.

Its not so much the functionality that is bothering me, its the fact that a tutorial will say "Go to Tools>Macro>Editor" and I am left scratching my head wondering where Tools went.

I really wish there was an option to go back to the classic menus as that's what I grew up using.

HOLY CRAP! I managed to get it working.

The X328CommX turned out to be a driver made in house. I was using Notepad++ to view its binary contents. While doing so I found some interesting text strings, so I searched the engineering servers for those strings in the hopes of finding the source. I was unable to find the source, but I did manage to find a installer for the driver (a bat file). All the installer really did was copy a couple of files and run regsvr32 on the files. The program works now. Thank you guys for taking time to try to help me out. Not gonna' lie, but I hope to never have to deal with VBA ever again. C++/C/VHDL FTW.