473,289 Members | 2,089 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,289 software developers and data experts.

BuiltinProperties DirectCast Fails

I get the following failure when trying to access the builtin properties;

An unhandled exception of type 'System.InvalidCastException' occurred in
resultsoutput.dll
Additional information: Specified cast is not valid.

In general terms the code is constructed as follows;

ModuleA
Public xlWb As Excel.Workbook

ModuleB
SubA
Dim prps As Microsoft.Office.Core.DocumentProperties
prps = DirectCast(xlWb.BuiltinDocumentProperties,
Microsoft.Office.Core.DocumentProperties)

This is using;
Framework 1.1
Excel 2002 SP3
Reference to COM Microsoft Excel 10.0 Object Library (Version 1.4)

I've been following the article by Ken Getz
(http://msdn.microsoft.com/library/de...-us/odc_vsto20
03_ta/html/ExcelObj.asp) which suggests the code should work. Ken's article
refers to Excel 2003, but all the objects he references are also in the
Microsoft Excel 10 COM object. I wondered whether this was a bug in the 2002
COM or I've missed something in my code.

Nov 20 '05 #1
6 2094
Try CType instead of DirectCast.
In this case, you're dealing with COM wrappers, and I have the nagging
feeling you're using a newer interface and trying to cast directly to an
older one. CType should call QueryInterface under the hood, so that if the
interface exists, it will get you a proper reference.

Hope that helps,

-Rob Teixeira [MVP]

"Mark Nethercott" <Ma*************@iFabre.com> wrote in message
news:up*************@TK2MSFTNGP09.phx.gbl...
I get the following failure when trying to access the builtin properties;

An unhandled exception of type 'System.InvalidCastException' occurred in
resultsoutput.dll
Additional information: Specified cast is not valid.

In general terms the code is constructed as follows;

ModuleA
Public xlWb As Excel.Workbook

ModuleB
SubA
Dim prps As Microsoft.Office.Core.DocumentProperties
prps = DirectCast(xlWb.BuiltinDocumentProperties,
Microsoft.Office.Core.DocumentProperties)

This is using;
Framework 1.1
Excel 2002 SP3
Reference to COM Microsoft Excel 10.0 Object Library (Version 1.4)

I've been following the article by Ken Getz
(http://msdn.microsoft.com/library/de...-us/odc_vsto20 03_ta/html/ExcelObj.asp) which suggests the code should work. Ken's article refers to Excel 2003, but all the objects he references are also in the
Microsoft Excel 10 COM object. I wondered whether this was a bug in the 2002 COM or I've missed something in my code.

Nov 20 '05 #2
Rob,
DirectCast will call QueryInterface to find the COM interface!

I will be very curious if CType works, where DirectCast fails.

Hope this helps
Jay

"Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
Try CType instead of DirectCast.
In this case, you're dealing with COM wrappers, and I have the nagging
feeling you're using a newer interface and trying to cast directly to an
older one. CType should call QueryInterface under the hood, so that if the
interface exists, it will get you a proper reference.

Hope that helps,

-Rob Teixeira [MVP]

"Mark Nethercott" <Ma*************@iFabre.com> wrote in message
news:up*************@TK2MSFTNGP09.phx.gbl...
I get the following failure when trying to access the builtin properties;
An unhandled exception of type 'System.InvalidCastException' occurred in
resultsoutput.dll
Additional information: Specified cast is not valid.

In general terms the code is constructed as follows;

ModuleA
Public xlWb As Excel.Workbook

ModuleB
SubA
Dim prps As Microsoft.Office.Core.DocumentProperties
prps = DirectCast(xlWb.BuiltinDocumentProperties,
Microsoft.Office.Core.DocumentProperties)

This is using;
Framework 1.1
Excel 2002 SP3
Reference to COM Microsoft Excel 10.0 Object Library (Version 1.4)

I've been following the article by Ken Getz

(http://msdn.microsoft.com/library/de...-us/odc_vsto20
03_ta/html/ExcelObj.asp) which suggests the code should work. Ken's

article
refers to Excel 2003, but all the objects he references are also in the
Microsoft Excel 10 COM object. I wondered whether this was a bug in the

2002
COM or I've missed something in my code.


Nov 20 '05 #3
Thanks for the suggestions. I'd already tried CType as an alternative, but
that fails as well.

Ken Getz's article is pretty clear on working with the DirectCast - I'll try
the code with the 2003 COM object

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:e7**************@TK2MSFTNGP09.phx.gbl...
Rob,
DirectCast will call QueryInterface to find the COM interface!

I will be very curious if CType works, where DirectCast fails.

Hope this helps
Jay

"Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
Try CType instead of DirectCast.
In this case, you're dealing with COM wrappers, and I have the nagging
feeling you're using a newer interface and trying to cast directly to an
older one. CType should call QueryInterface under the hood, so that if the
interface exists, it will get you a proper reference.

Hope that helps,

-Rob Teixeira [MVP]

"Mark Nethercott" <Ma*************@iFabre.com> wrote in message
news:up*************@TK2MSFTNGP09.phx.gbl...
I get the following failure when trying to access the builtin properties;
An unhandled exception of type 'System.InvalidCastException' occurred in resultsoutput.dll
Additional information: Specified cast is not valid.

In general terms the code is constructed as follows;

ModuleA
Public xlWb As Excel.Workbook

ModuleB
SubA
Dim prps As Microsoft.Office.Core.DocumentProperties
prps = DirectCast(xlWb.BuiltinDocumentProperties,
Microsoft.Office.Core.DocumentProperties)

This is using;
Framework 1.1
Excel 2002 SP3
Reference to COM Microsoft Excel 10.0 Object Library (Version 1.4)

I've been following the article by Ken Getz

(http://msdn.microsoft.com/library/de...-us/odc_vsto20
03_ta/html/ExcelObj.asp) which suggests the code should work. Ken's

article
refers to Excel 2003, but all the objects he references are also in the Microsoft Excel 10 COM object. I wondered whether this was a bug in

the 2002
COM or I've missed something in my code.



Nov 20 '05 #4
Yes, you're absolutely right. That's what I get for posting while
multi-tasking *sigh*

OK, this seems like a similar issue to a co-worker had.
Try this Mark - Use reflection on the object reference you do have to get
all implemented interfaces.
Also use Reflection to get the GuidAttribute from each (including the
GuidAttribute on the object ref's class).

Next, check to see that these are in fact the registered interfaces for
Excel in the system registry (based on the GUIDs).
I believe the problem may in fact be that you are trying to cast to a newer
version of the interface, which an older version of Excel might not provide
(or another such scenario). It would also help to know what version of the
PIAs you are using vs. what version of Office (and which PIAs have you
installed on that system).

-Rob Teixeira [MVP]

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:e7**************@TK2MSFTNGP09.phx.gbl...
Rob,
DirectCast will call QueryInterface to find the COM interface!

I will be very curious if CType works, where DirectCast fails.

Hope this helps
Jay

"Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
Try CType instead of DirectCast.
In this case, you're dealing with COM wrappers, and I have the nagging
feeling you're using a newer interface and trying to cast directly to an
older one. CType should call QueryInterface under the hood, so that if the
interface exists, it will get you a proper reference.

Hope that helps,

-Rob Teixeira [MVP]

"Mark Nethercott" <Ma*************@iFabre.com> wrote in message
news:up*************@TK2MSFTNGP09.phx.gbl...
I get the following failure when trying to access the builtin properties;
An unhandled exception of type 'System.InvalidCastException' occurred in resultsoutput.dll
Additional information: Specified cast is not valid.

In general terms the code is constructed as follows;

ModuleA
Public xlWb As Excel.Workbook

ModuleB
SubA
Dim prps As Microsoft.Office.Core.DocumentProperties
prps = DirectCast(xlWb.BuiltinDocumentProperties,
Microsoft.Office.Core.DocumentProperties)

This is using;
Framework 1.1
Excel 2002 SP3
Reference to COM Microsoft Excel 10.0 Object Library (Version 1.4)

I've been following the article by Ken Getz

(http://msdn.microsoft.com/library/de...-us/odc_vsto20
03_ta/html/ExcelObj.asp) which suggests the code should work. Ken's

article
refers to Excel 2003, but all the objects he references are also in the Microsoft Excel 10 COM object. I wondered whether this was a bug in

the 2002
COM or I've missed something in my code.



Nov 20 '05 #5
Yes, you're absolutely right. That's what I get for posting while
multi-tasking *sigh*

OK, this seems like a similar issue to a co-worker had.
Try this Mark - Use reflection on the object reference you do have to get
all implemented interfaces.
Also use Reflection to get the GuidAttribute from each (including the
GuidAttribute on the object ref's class).

Next, check to see that these are in fact the registered interfaces for
Excel in the system registry (based on the GUIDs).
I believe the problem may in fact be that you are trying to cast to a newer
version of the interface, which an older version of Excel might not provide
(or another such scenario). It would also help to know what version of the
PIAs you are using vs. what version of Office (and which PIAs have you
installed on that system).

-Rob Teixeira [MVP]

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:e7**************@TK2MSFTNGP09.phx.gbl...
Rob,
DirectCast will call QueryInterface to find the COM interface!

I will be very curious if CType works, where DirectCast fails.

Hope this helps
Jay

"Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
Try CType instead of DirectCast.
In this case, you're dealing with COM wrappers, and I have the nagging
feeling you're using a newer interface and trying to cast directly to an
older one. CType should call QueryInterface under the hood, so that if the
interface exists, it will get you a proper reference.

Hope that helps,

-Rob Teixeira [MVP]

"Mark Nethercott" <Ma*************@iFabre.com> wrote in message
news:up*************@TK2MSFTNGP09.phx.gbl...
I get the following failure when trying to access the builtin properties;
An unhandled exception of type 'System.InvalidCastException' occurred in resultsoutput.dll
Additional information: Specified cast is not valid.

In general terms the code is constructed as follows;

ModuleA
Public xlWb As Excel.Workbook

ModuleB
SubA
Dim prps As Microsoft.Office.Core.DocumentProperties
prps = DirectCast(xlWb.BuiltinDocumentProperties,
Microsoft.Office.Core.DocumentProperties)

This is using;
Framework 1.1
Excel 2002 SP3
Reference to COM Microsoft Excel 10.0 Object Library (Version 1.4)

I've been following the article by Ken Getz

(http://msdn.microsoft.com/library/de...-us/odc_vsto20
03_ta/html/ExcelObj.asp) which suggests the code should work. Ken's

article
refers to Excel 2003, but all the objects he references are also in the Microsoft Excel 10 COM object. I wondered whether this was a bug in

the 2002
COM or I've missed something in my code.



Nov 20 '05 #6
Thanks Rob for the input.

You were right, in the end I had to use reflection to contort my way through
the COM interface.
It took a while to figure out & I relied heavily on the help of Tom Annetts
@ Experts-Exchange.

The full thread can be found at;

http://www.experts-exchange.com/Prog..._20973995.html

I've included the final function here for completeness. I've only tested it
under XP SP3 & Excel 2002, where it works fine;

Sub SetProperty(ByVal xlWB As Excel.Workbook, ByVal PName As String, ByVal
PValue As Object, _
ByVal isPropCustom As Boolean)

'This function sets the value of a property.
'
'The parameters passed to the function are as follows:
'
'xlWB A reference to the the workbook whose property is to
be set.
'PName A string containing the name of the property
'PValue A variant containing the value of the property
'isPropCustom A boolean indicating whether the property is a
Custom Document Property.

Dim result As Object
Dim PType As Long
Dim isLinkToContent As Boolean = False
Dim LinkSource As Object = Nothing

Select Case VarType(PValue)
Case vbBoolean
PType =
Microsoft.Office.Core.MsoDocProperties.msoProperty TypeBoolean
Case vbDate
PType = Microsoft.Office.Core.MsoDocProperties.msoProperty TypeDate
Case vbDouble, vbLong, vbSingle, vbCurrency
PType = Microsoft.Office.Core.MsoDocProperties.msoProperty TypeFloat
Case vbInteger
PType = Microsoft.Office.Core.MsoDocProperties.msoProperty TypeNumber
Case vbString
PType = Microsoft.Office.Core.MsoDocProperties.msoProperty TypeString
Case Else
PType = Microsoft.Office.Core.MsoDocProperties.msoProperty TypeString
End Select

If isPropCustom Then
xlWB.CustomDocumentProperties.GetType().InvokeMemb er("Add",
BindingFlags.InvokeMethod, _
Nothing, xlWB.CustomDocumentProperties, New Object() {PName,
isLinkToContent, PType, PValue, LinkSource})
Else
result = xlWB.BuiltinDocumentProperties.GetType().InvokeMem ber("Item",
BindingFlags.GetProperty, _
Nothing, xlWB.BuiltinDocumentProperties, New Object() {PName})
result.GetType().InvokeMember("Value", BindingFlags.SetProperty,
Nothing, result, New Object() {PValue})
End If

End Sub
"Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Yes, you're absolutely right. That's what I get for posting while
multi-tasking *sigh*

OK, this seems like a similar issue to a co-worker had.
Try this Mark - Use reflection on the object reference you do have to get
all implemented interfaces.
Also use Reflection to get the GuidAttribute from each (including the
GuidAttribute on the object ref's class).

Next, check to see that these are in fact the registered interfaces for
Excel in the system registry (based on the GUIDs).
I believe the problem may in fact be that you are trying to cast to a newer version of the interface, which an older version of Excel might not provide (or another such scenario). It would also help to know what version of the
PIAs you are using vs. what version of Office (and which PIAs have you
installed on that system).

-Rob Teixeira [MVP]

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:e7**************@TK2MSFTNGP09.phx.gbl...
Rob,
DirectCast will call QueryInterface to find the COM interface!

I will be very curious if CType works, where DirectCast fails.

Hope this helps
Jay

"Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
Try CType instead of DirectCast.
In this case, you're dealing with COM wrappers, and I have the nagging
feeling you're using a newer interface and trying to cast directly to an older one. CType should call QueryInterface under the hood, so that if the interface exists, it will get you a proper reference.

Hope that helps,

-Rob Teixeira [MVP]

"Mark Nethercott" <Ma*************@iFabre.com> wrote in message
news:up*************@TK2MSFTNGP09.phx.gbl...
> I get the following failure when trying to access the builtin properties;
>
> An unhandled exception of type 'System.InvalidCastException' occurred in
> resultsoutput.dll
> Additional information: Specified cast is not valid.
>
> In general terms the code is constructed as follows;
>
> ModuleA
> Public xlWb As Excel.Workbook
>
> ModuleB
> SubA
> Dim prps As Microsoft.Office.Core.DocumentProperties
> prps = DirectCast(xlWb.BuiltinDocumentProperties,
> Microsoft.Office.Core.DocumentProperties)
>
> This is using;
> Framework 1.1
> Excel 2002 SP3
> Reference to COM Microsoft Excel 10.0 Object Library (Version 1.4)
>
> I've been following the article by Ken Getz
>

(http://msdn.microsoft.com/library/de...-us/odc_vsto20 > 03_ta/html/ExcelObj.asp) which suggests the code should work. Ken's
article
> refers to Excel 2003, but all the objects he references are also in the > Microsoft Excel 10 COM object. I wondered whether this was a bug in the 2002
> COM or I've missed something in my code.
>
>
>



Nov 20 '05 #7

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

4
by: Andreas Klemt | last post by:
Hello, what has the better performance and what are you using? Dim myObj As Object = 70 a) Dim myInt As Integer = DirectCast(myObj, Integer) b) Dim myInt As Integer = Convert.ToInt32(myObj) ...
11
by: Tubs | last post by:
i am attempting to write something which can morph itself to whatever comes in and get the value property from it but i don't know what type it is until runtime. I am therefore trying to use...
6
by: Ot | last post by:
I apparently have a bit to learn about Casting and Conversion. I have been thinking of them as the same but a discussion in another thread leads me to believe that this is wrong thinking. I...
5
by: Michael Ramey | last post by:
Hello, There are quite a few ways to convert one object, say an integer to a string. Dim myStr as string dim myInt as integer = 123 myStr = cstr(myInt) myStr = myInt.toString()
7
by: Brian Henry | last post by:
is there any speed diffrences between doing Ctype or directcast? I know about the inherite diffrences, but process usage time wise, does one take up more cycles then the other? thanks
1
by: iwdu15 | last post by:
can anyone explain the directcast code...ive tried using it and lookin it up but im lookin for an easy definition and how it works...ive tried using it before byut it throws errors saying it can...
4
by: Vagabond Software | last post by:
Here is the code: Dim amountDue As Double amountDue = Math.Round(DirectCast(strOrderTotal, Double), 2) This code produces an invalid cast exception. The String variable strOrderTotal...
2
by: lothar.behrens | last post by:
Hi, I am trying to load an assembly at runtime (plugin). Having the object (as Object), I like to cast it to the interface. The interface is defined as follows: Public Interface...
9
BezerkRogue
by: BezerkRogue | last post by:
I am using this code to enter records into a SQL DB. It fails after 11 records. Can anyone tell me what's wrong? Protected Sub cmdSubmit_Click(ByVal sender As Object, ByVal e As...
2
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 7 Feb 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:30 (7.30PM). In this month's session, the creator of the excellent VBE...
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
0
by: Aftab Ahmad | last post by:
Hello Experts! I have written a code in MS Access for a cmd called "WhatsApp Message" to open WhatsApp using that very code but the problem is that it gives a popup message everytime I clicked on...
0
by: ryjfgjl | last post by:
ExcelToDatabase: batch import excel into database automatically...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: marcoviolo | last post by:
Dear all, I would like to implement on my worksheet an vlookup dynamic , that consider a change of pivot excel via win32com, from an external excel (without open it) and save the new file into a...
1
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: Vimpel783 | last post by:
Hello! Guys, I found this code on the Internet, but I need to modify it a little. It works well, the problem is this: Data is sent from only one cell, in this case B5, but it is necessary that data...
1
by: PapaRatzi | last post by:
Hello, I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.