We have log sheets that look into SolidEdge file properties to populate an Excel spreadsheet with those properties. Since we have switched to SolidEdge 2019 they no longer update. The debugger catches on the Solid Edge properties. Did the label for the properties we need to reference change with the new version? I apologize for my limited knowledge.
Short term: install Solid Edge View & Markup to get access to the 32-bit dll files.
Long term: update your custom code to support 64-bit as View & Markup is going away.
All documented in the Solid Edge readme file.
@uk_dave gave the short term solution and the long term fix...
Longer answer so you may understand better...
Your existing code is built using Solid Edge 32-bit libraries.
Starting with SE2019 we no longer deliver 32-bit dll files.
Therefore your existing code will no longer run.
However, we still provide 32-bit dll files with SE2019 View & Markup.
Therefore if you install SE2019 View & Markup on your workstation along with Solid Edge your existing code will then work again.
However, that is a short-term solution as View & Markup is end of life.
Going forwards you need to recompile your existing code to use the Solid Edge 64-bit libraries.
Again, all documented in the SE2019 readme file.
in this similar post https://community.plm.automation.siemens.com/t5/Solid-Edge-Developer-Forum/VBA-with-Excel-CreateObje... my advice was to renew the COM reference in the 64-bit Excel VBA project and use New instead of CreateObject. The latter seems already to be done in your screen shot of the VBA program.
But I also see that your VBA code is using the former FileSystemObject component, which is definitely an old 32-bit VB6 component used by 32-bit VB6 and VBA. So I doubt you ever will be able to get your VBA code get running with 64-bit COM objects, even if you have Excel 64-bit installed.