Hi
I will try to describe a strange issue that I have come across.
We are creating pdf files, both on server and on client. We let the printerjobsettings give us a file name, that is created somehow in the kernel. This file name is normally called something like:
(..)\AppData\Local\Temp\AXT1435.tmp
We copy this file to the mail attachments folder on the server, change the extension to ".pdf" and remove the original temp file. If we create another file, Ax normally creates a new temp file with a totally different filename, e.g "AXT7355.tmp"
Our problem now, is that some of our customers do not get temp file names like this. Instead, they get file names like "AXT1.tmp" or "Axt53.tmp". The worst thing is, that a new temp file often (or always) gets the same name as the last one. Probably since the last one has been deleted. This seems to be an issue on the server side, not on the client side. Client temp files always get a new totally different name, even if the last file has been deleted.
Does anyone know how this filename gets created? Is there some kind of parameter or system variable that I can change, so that all temp files get random names and definitely not names consisting of only one single digit after the AXT prefix.
I have tried to set break points in all methods that are creating temp file names on client or server, but it seems like the printerjobsettings class does not use these methods.
Thanks in advance for your input.
/Jonas
