microsoft visual basic for applications error solidworks

Portability (multi-platform use) depends on operating systems supporting Excel or VBA.

Usability (ease of use) arises from both the application and Excel’s user interface (UI) and user experience (UX) design.

Excel VBA is a hosted language (Excel being the host), so some of these attributes derive from Excel itself. Note, I did originally post this in the VB.Net section by mistake, so I've re-posted it here and removed that thread.Not all these attributes derive from Excel VBA code though. I tried going through the registry but without specific direction it was useless. Has been updated and accidentally unregistered/deleted something.

I'm curious whether there is a better way to reference the excel object library that would be more robust? Or possibly something in the background I've tried with the Excel 16.0 object library and it made no difference.Īny thoughts on where this problem could be coming from? I know it's not code specific, since it works elsewhere. (Computer is currently running Excel 2019). The standard throughout the workplace is the Excel 14.0 object library. I've tried with different object libraries.

This brings up an error 'ActiveX cannot create object.' Set xlApp = CreateObject('Excel.Application') Using this code for late-binding does not work either, however this brings up an ActiveX error. Set swModel = swApp.ActiveDoc Set xlApp = New Excel.Application Here is a snippet of the code: (error occurs on line three) Dim xlApp As Excel.Application It's currently running fine on two other network computers,Īnd was running fine on this one until this morning. The code is a VBA macro (not VB.Net) from Solidworks (CAD software) that opens and reads an Excel sheet before returning back to Solidowrks. This is a recent problem that just appeared this morning.

Microsoft visual basic for applications error solidworks