M
mr_unreliable
the missing owcSpreadsheet typelib elements?
I have been using the owcSpreadsheet control (v10) in vb (classic)
and vbScript with some modest success.
There is one troubling thing. In vb you get hinting (microsoft
calls it "intelli-sense") to the extent of the methods and properties
provided by the control's typelib.
I noticed that some things I wanted to do were "missing". However,
if I went over to microsoft excel, and developed some spreadsheet
macro code, that code could then be carried back over and run in
vb to drive the owcSpreadsheet too.
In other words, there was more capability to the owcSpreadsheet
than was evident by looking in its typelib.
I resolved the problem somewhat by bringing into the vb environment
a reference to the "microsoft excel (vx.x) object library". That allows
me to see the methods and properties that excel (and by implication
owcSpreadsheet) is supporting by using the object browser, but still
the "hinting" is not available for those excel methods and properties.
Here's the question(s). Was this intended? Is there some "hidden"
owcSS methods and properties which make owcSS compatible with
excel, but which have been purposely left out of the typelib?
I haven't been able to find this aspect of owcSS documented, and
from reading this ng, it appears that the only "good" documentation
is that book that is frequently referred to, but NOT msdn.
Is that observation accurate?
I do realize that the typelib is a separate thing from the code
itself, and that the original component coders will usually generate
the typelib using a "typelib definition language" plus a typelib
compiler. So the typelib will only reflect the capability of the
component to the extent that the developer wishes to expose by
inclusion in the typelib. Also, I understand that it is possible
to comb through the code and make a "complete" listing of the
interfaces from scratch. Has this ever been done with owcSS?
cheers, jw
I have been using the owcSpreadsheet control (v10) in vb (classic)
and vbScript with some modest success.
There is one troubling thing. In vb you get hinting (microsoft
calls it "intelli-sense") to the extent of the methods and properties
provided by the control's typelib.
I noticed that some things I wanted to do were "missing". However,
if I went over to microsoft excel, and developed some spreadsheet
macro code, that code could then be carried back over and run in
vb to drive the owcSpreadsheet too.
In other words, there was more capability to the owcSpreadsheet
than was evident by looking in its typelib.
I resolved the problem somewhat by bringing into the vb environment
a reference to the "microsoft excel (vx.x) object library". That allows
me to see the methods and properties that excel (and by implication
owcSpreadsheet) is supporting by using the object browser, but still
the "hinting" is not available for those excel methods and properties.
Here's the question(s). Was this intended? Is there some "hidden"
owcSS methods and properties which make owcSS compatible with
excel, but which have been purposely left out of the typelib?
I haven't been able to find this aspect of owcSS documented, and
from reading this ng, it appears that the only "good" documentation
is that book that is frequently referred to, but NOT msdn.
Is that observation accurate?
I do realize that the typelib is a separate thing from the code
itself, and that the original component coders will usually generate
the typelib using a "typelib definition language" plus a typelib
compiler. So the typelib will only reflect the capability of the
component to the extent that the developer wishes to expose by
inclusion in the typelib. Also, I understand that it is possible
to comb through the code and make a "complete" listing of the
interfaces from scratch. Has this ever been done with owcSS?
cheers, jw