![]() ![]() I wondered if this was some limitation of Excel under an Office subscription plan, so I checked on my home PC (has pretty close specs - Win10 Pro 圆4, an Office 365 home subscription and the identical Excel release) and LabVIEW Community Edition installed there appeared to work fine for opening an Excel.Application reference. My Excel version (File->Account->About Excel) shows “Microsoft Excel for Microsoft 365 MSO (7.21062) 32-bit”. System OS is Win10 Enterprise (3), 圆4, and LabVIEW is 19.0.1f3 (32-bit). I’m not having much success online with searching Microsoft for this error. It’s when I wire that to an Automation Open node and run that I get an error (-2147319765, or x8002802B), which just says “Element not found”. I’ve actually troubleshot it to beneath the toolkit anyway – if I just drop an ActiveX reference on the diagram, I can browse to the type library “Microsoft Excel 16.0 Object Library 1.9” and get a reference to “Application (Excel.Application.16)”. As far as I can verify, the Report Generation toolkit is properly installed and licensed on both my LV 2019 SP1 and my LV 2020 installations. This means none of the Report Generation toolkit VIs work. None of the ActiveX automation stuff seems to work, at all – I get back a pretty generic error and so far am stumped as to cause. I’ve discovered that I have some sort of problem with my corporate laptop’s installation of Office/Excel with respect to LabVIEW. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |