Option Strict On Disallows Late Binding -- What to do?

  • Thread starter Thread starter DK
  • Start date Start date
D

DK

This particular area of the program builds a Excel spreadsheet for the
user to manipulate further. After turning Option Strict On and
correcting everything I can the following line remains -- any ideas
how to reconstruct this so it doesn't think its a late bound object?

xlWS.Cells(row, col).value = ObjColumn.HeaderOne & " " &
ObjColumn.HeaderTwo

XLWS is defined as an Excel.Worksheet and xlWS.Cells(row,col).value
apears to be late bound -- what do I need to use in place of this?
 
Try to caste the Cells(...) call into the object type you expect (a Range?).
CType(xlWS.Cells(row, col), Excel.Range).value=...
Or something like that.
 
DK,

The way I would do it, was using the intelligence, as xlWS is correct then
it will give after the dot what you can use.

In other words, type it over again.

If there then is something that is not in your intelligence, then you have
to (direct)cast it, to a "type" that contain then what you are using.

Cor
 
DK,

The way I would do it, was using the intelligence, as xlWS is correct then
it will give after the dot what you can use.

In other words, type it over again.

If there then is something that is not in your intelligence, then you have
to (direct)cast it, to a "type" that contain then what you are using.

Cor
Click to expand...

Agreed but it looks nasty:
xlWS.Range(xlWS.Cells(row, col), xlWS.Cells(row, col)).Value =
ObjColumn.HeaderOne & " " & ObjColumn.HeaderTwo
 
Back
Top