Advanced VB/Office Guru™ Word SpellChecker™.NET

[RobDog888]

lol yup

If your creating a setup package and have the PIAs then you shouldnt have an issue but then again I havent had any other version other then 2003 so...

Its supossed to be that when you use the PIAs you dont have to worry about versioning. You can always use late binding and remove the references to Office and Word. Then you would have to go and cast all your types correctly so you can use Option Strict still.

Man, I got to stop posting and get some sleep. Should be up in a few hours though as I have to be up before 9am. 4.5 hours sleep should be good for a while.

[mikeschulze]

Ok, Bare with me... late binding has created a load of fun for me. I can see where this is going to solve my compatibility issues, but yeesh, VS2005 likes to complain about everything. Also, since I'm not familiar with working with MSWord this way, this is a bit of a learning curve --and to do it.. option stric has to be off.. late binding is not allowed otherwise... so no intellisense... AH!

Anyways... I've gotten this far with this challenge...

1. when I declare the moApp and oDoc as objects, it likes to complain about all the references to word.wsWindowState (says 'word' is not delared)

2. also complains about moApp.Dialogs(word.aWdWordDialog... (says 'word' is not declared)

3. It doesn't like the Direct Cast statement (says 'word.application' is not defined)

if I replace the word. with moApp., and I sub in object for word.application in the direct cast statement, it builds fine, but it throws errors on the btn_click event saying that Public member 'WdWindowState' on type 'ApplicationClass' not found.

I'm finding I don't know enough about how to talk to Word. I think. Oi.