save as dlg from word integration

Ben_inform

Hi Forum

We have an issue with printing from Word on Worksite PCs.

We use CMS for all our client billing & related document generation via Word. To generate Word documents, CMS uses "DocuDraft" as an intermediary if you like, to assemble all the documents that are produced. In basic theory - its a type of merge DocuDraft organises between the info from the database into an RTF template. However no user intervention is required. The document you request from CMS is just launched, printed and closed - its not saved at any point & is 'disposable' if you like.

The way it works is this:
* RTF template is launched into Word (if its open, else it starts up a WinWord.exe)
* Info from CMS is pumped into relevant fields via DDE connection
* Doc is printed
* Doc is closed.

Until now, this all works fine. No prompting of the user and when they're doing batches of documents, they all go through one after the other. When Worksite is installed, it is stopping after printing the document with the message "Do you want to save changes to document x? Yes/No" which is getting everyone quite frustrated.

If we unregister the integration dll first then it all works fiine - the merge, print, close occurs seamlessly. As soon as we re-register the dll, we get the prompt back again.

Is there a way we can diable the save change dialog ?

DaleN

Hi Ben,

If you can get into the macro code for the process you could try adding "ActiveDocument.Saved = True" before closing the file to change the document status. The WorkSite integration shouldn't look at the file if there are no "changes" to be saved. Alternatively, you could create a sink on the extensibility object and add some code to the DocumentBeforeClose2 event that sets the IgnoreIManageClose property to TRUE. Let me know if you need a more detailed sample.

Regards,
Dale