Issue with MS Word COM object and WorkSite Integration

msheridan69

Hi,

We are using the default office integration such as checkin/checkout when open/closeing document is word. However, we have a .NET application that interops with Worksite and Word. Our app creates a word document then checks it into WorkSite. Later, we programmatically check the document out of WorkSite to a local ‘working’ folder where we programmatically open it again in Word using the Word.Application.Documents.Open() method. This all works without any apparent issues.

The user makes changes to the document and then attempts to save/close the document from word. This action triggers the integrated WorkSite/Word Checkin process. This process fails reporting it can’t complete because it doesn’t have a document reference. It appears that programmatically opening a document via the standard Word COM interface bypasses WorkSite integration where the document reference is initialised. Is there a way to open the document in Word, without displaying the FileOpen Dialog, so the WorkSite integration module can create a reference to the document?

Thanks,
Martin

guido1

I'm not sure I've fully understood what your objective is, but if you've already successfully checked in the document created by your .NET app you should be able to use the IMANEXTLib.OpenCmd object (part of IManExt.dll) to check out the document in an integrated mode. There is an example of this in the SDK documentation.

Essentially the OpenCmd command will check out and download the document to the local drive (C:\NrPortbl\..), and return you the full path. All you then need to do is use the Word object model to open the document (as you're already doing), and then let the normal Worksite COM integration will do the rest.

In other words, when the user closes the document that you've programatically opened in Word the COM integration will sense that the document is profiled in Worksite and automatically check it back in.