Word Automation - locking files

Miklos_Hollender

Now that's strange. A client is using some custom-made Word Automation from Navision that's been working for years and now it's broken, maybe due to a Word/operation system/whatever upgrade. The problem is that even though WordApp.Quit is called, the Word doc stays locked (even though it's not open) by that user. And the document is on a network drive, everybody is using that copy, so nobody else can use that automation function anymore.

I have a faint gut feeling that the whole stuff is badly written, because for mail merge I think one should use a .DOT, not a .DOC, but instead it's a .DOC that then gets modified by mail merge, printed, and then not saved.

But anyway, it worked for years. I think maybe the current versions of Word might be too strict about it - a modified document stays locked even if you close it without saving?...

Anyway, what I suggested to them to copy a copy to a local drive and use from there. I hope Word doesn't lock if it's the same user...

Any ideas?

Miklos_Hollender

Might be the reason that the Open2000 function is used for opening the document?

wakestar

it sounds like the Open2000 - method is used for opening Word2000- documents.

However, Open2000 is not intended to be used directly from the code.
http://msdn2.microsoft.com/en-us/librar ... 2000(VS.80).aspx

Miklos_Hollender

Thanks... but it worked when Word 2000 was installed... now I think it's Word 2003 but the document is Word 2000 so the code should still be appropriate?

wakestar

I would try it with the default method 'Open'.

Miklos_Hollender

...but converting the file first to 2003 format, right?...

wakestar

No, let the method 'Open' find out if it is a Word2000 or Word2003 document.