Office 365 update kills VB.Net compile

  • Thread starter Thread starter Shady Brady Hat
  • Start date Start date
S

Shady Brady Hat

Guest
Because of a repeated failure of an Office/365 update I had to remove and re-install Office/365. This went with no problems. Then I went back a project I am working on and a no error project suddenly had 63 errors on attempt to build. The root of the failure is these two statements failing with a statement that they are not defined. Checked references and they still contain the pointers to Microsoft Office15 Object library and Microsoft16 Object library. This just doesn't make any sense.
Public oExcel As Excel.Application
Public oWorkBook As Excel.Workbook


Gene

Continue reading...
 

Similar threads

S
Office 365 update kills VB.Net compile
Replies
0
Views
174
Shady Brady Hat
S
P
VB.Net reference to COM "Microsoft Excel 16.0 Object Library": No WorkbookQuery (???)
Replies
0
Views
337
Peter Ferber
P
B
Microsoft Excel 15.0 Object Library of COM - Visual Studio 2017 and Office 365
Replies
0
Views
137
BIManish
B
Y
Fail to compile after trying add ons to connect to office word
Replies
0
Views
95
YigalB
Y
N
VB.NET My.Settings Values - Where Is The (Elusive) Primary Store?
Replies
0
Views
96
NotchersMine
N
Back
Top