Uh, isn't that what he's doing already? He's using generic Word.Application (rather than the version specific ProgId)...

I think the problem is something different since the error doesn't appear to occur on instantiation but when the doc is opened...

+++ Rick ---

>Hi Allan,
>
>When you are working with different versions of Word or Excel, you will need to write your Word interfacing with VB.NET, using Option Strict Off or use Reflection in C# (or VB.NET). This allows for late binding so the compiler does not link to a specific version. Here is a MSDN article that explains this and provides examples:
>
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odc_vsto2003_ta/html/OffCSharp.asp
>
>
>>Hi Bonnie,
>>
>>You're right. I have OfficeXP, the client has Office 2000.
>>
>>>Your problem is probably different versions of Word on your client's box than what's on your dev box. Unfortunately, there are slight differences in how Word is opened in Word 2000 vs Word 2003. Which do you have and which does your client have?
>>>
>>>~~Bonnie
>>>
>>>
>>>>Hi,
>>>>
>>>>Just trying to open a Word Document using VB.NET.
>>>>
>>>>This code works on my dev box.
>>>>
>>>>

>>>>
>>>>Dim wrdDoc As Word.Document
>>>>Dim wrdApp As Word.Application
>>>>Dim strLargEnvTemplate as String = "C:\EnvTemplate.doc"
>>>>
>>>>wrdApp = CType(CreateObject("Word.Application"), Word.Application)
>>>>wrdApp.Visible = True
>>>>
>>>>wrdDoc = wrdApp.Documents.Open(strLargEnvTemplate)
>>>>
>>>>

>>>>
>>>>However, at the client site, an exception is created on
>>>>
>>>>

>>>>
>>>>wrdDoc = wrdApp.Documents.Open(strLargEnvTemplate)
>>>>
>>>>'The error message is "Object Reference not set to instance of an object"
>>>>
>>>>'Word is instantiated OK - but the document will not load...
>>>>

>>>>
>>>>Any idea why the code works on my dev box but generates an exception on the production PC's?
>>>>
>>>>Is there a better way to open a Word Document from VB.NET?