Word automation and printer spooler document name

[XAimeElle]

I am developping code to print forms with Word automation. A typical print job will have 20 forms to print in sequence. So to improve performance, we start Word only once, add a new document, update the document, print, close the document and proceed with the next document. Since we dont save the document, when we print, the document has a generic name like "Document2".

Trying to change the open document name result in a "Read only" error message.
Is there a way to change the spooler document name. Thanks

FWordApp.Documents.Add(Template:=FDocumentName,NewTemplate:=False);
FWordApp.Documents.Item(FWordApp.Documents.Count).Activate;

te;

[Hack]

Welcome to DevX

After doing the update, how about doing a SaveAs: and giving each document its on unique name then print and close.

[XAimeElle]

That would work, but our software often runs on a file servers, and worse on Citrix servers. Permissions to write temporary files not easy to get from our customers...so it would be difficult. However, I have to admit that several applications do create temporary files, why not ours. I am not too sure where I can ask Windows for a valid temporary file location.

[Hack]

Well, it sounds like your choices are pretty limited.

Either stick with the generic file names you have now, or find a spot to do a SaveAs

Is it a customer that is complaining about the generic Document1, Document2, etc file names?

[XAimeElle]

Its just me who is trying to finish this programming right. I will investiguate the SaveAs. Thanks.

[Hack]

I don't see why someone would have a problem giving you some temp space with the proviso that you keep it cleaned up.

[JBourgeois]

Unless it has been blocked by administrators, your application can generally write with confidence to the ApplicationData directory, which you can retrieve with

system.Environment.GetFolderPath (System.Environment.SpecialFolder.ApplicationData)

You might also try with some of the other folders listed through the SpecialFolder enumeration.

Another avenue would be to use Isolated Storage (look it up in MSDN) which is also usually opened for use.