Yeah - 2003 is fine. I remove the reference "microsoft word 11.0" and replaced with "microsoft word 12.0" and it errors straight away. (
A first chance exception of type 'System.Runtime.InteropServices.SEHException' occurred)
I can't figure out what is going on with it. I'm thinking about completely rewriting it to see if i can solve it. I'd like it to work for both 2003 and 2007 versions of word, but i don't know how lucky i will be.
Any more ideas.. .I'm a bit of a novice by the way.
Thanks.
Aaron
> It works with Word 2k3, you stated.
> What happens if you switch the Interop assembly in yr project references
[quoted text clipped - 36 lines]
>>
>> Aaron.
Hi Aaron,
> Yeah - 2003 is fine. I remove the reference "microsoft
> word 11.0" and replaced with "microsoft word 12.0" and
[quoted text clipped - 6 lines]
> solve it. I'd like it to work for both 2003 and 2007
> versions of word, but i don't know how lucky i will be.
How about this article?
http://support.microsoft.com/default.aspx?scid=kb;en-us;313
104
Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update
Jun 17 2005)
http://www.word.mvps.org
This reply is posted in the Newsgroup; please post any
follow question or reply in the newsgroup and not by e-mail
:-)
Perry - 31 Jan 2007 19:28 GMT
Hmm, Cindy that's interesting...
Now translate that into VB.net ... hahaha
But, that really makes sense and I've stumbled accross other issues
with more less the same problem.
Indeed, optional parameters work slightly different in .NET
Good thinking !!
Chrs,
Perry
> Hi Aaron,
>
[quoted text clipped - 23 lines]
> follow question or reply in the newsgroup and not by e-mail
> :-)