Access/VBA doesn't understand ComPort data after upgrade to Win11.

[Praedico]

I have an Access DB that can (in Windows10) get data from a GPS receiver assigned to a com port.
The organization has decided to upgrade our computers to Windows 11, now Access/VBA no longer understands the data coming from the GPS receiver.
I am adding an image showing the "data" Access sees when it looks at the com port. Basically, a bunch of squares instead of the alphanumeric data that normally comes through.

Any ideas on how I can get it to understand the data again?

Thanks in advance

 

[Micron]

Is that your actual output? The vbe cannot replicate certain fonts, although I think it usually represents them as question marks (can't remember exactly but they might be upside down). When Window version was updated you may have lost a driver for the port(s). I'd check to see if any drivers are listed as missing or whatever the classification is. A post here suggests getting the latest driver

Problems under Windows 11 with normal Serial Port acess and with USB to Serial Access

Hello I encounter some problems under Windows 11 23H2 to access a simple Serial Port under .NET in C#.My earlier installations with Windows 10 and earlier..

techcommunity.microsoft.com

 

[Praedico]

Is that your actual output? The vbe cannot replicate certain fonts, although I think it usually represents them as question marks (can't remember exactly but they might be upside down). When Window version was updated you may have lost a driver for the port(s). I'd check to see if any drivers are listed as missing or whatever the classification is. A post here suggests getting the latest driver

Problems under Windows 11 with normal Serial Port acess and with USB to Serial Access

Hello I encounter some problems under Windows 11 23H2 to access a simple Serial Port under .NET in C#.My earlier installations with Windows 10 and earlier..

techcommunity.microsoft.com

Yes, those squares in the image are what Access/VBA is interpreting from the com port. It works fine in other software, it's only broken in the Office products (I get the same result for similar code in Excel). I agree it's probably a driver issue. I'll give it to the smarter people in our organization to see if they can solve it. I'll leave this open for a bit longer to see if anyone pops on with a different insight, and/or reply to myself with the fix if/when I find one.
Thank you.

 

[Micron]

Good luck! Please do post the solution if you get one.