Skip to main content

We have a customer that has a file-server environment set up.  They are trying to launch wordpad from the client and they get told that the application cannot open the file.

Thanks for any insight!

We have a customer that has a file-server environment set up.  They are trying to launch wordpad from the client and they get told that the application cannot open the file.

Thanks for any insight!

Hello Joanne,

Normally the print output files are stored in the working directory of the application. You can check this by executing the ProcScript function $ldir before printing.

It, however is also possible to reroute the files in the ASN (check for anything matching the pattern *.p??). So, if you print to a file then you could also check, after the print statement, the value of the following statement ($result contains the file name of the print output file):

vFullPrintFileName = $item("FULLPATH", $fileproperties($result))

I hope this helps.

Kind regards,
Daniel

We have a customer that has a file-server environment set up.  They are trying to launch wordpad from the client and they get told that the application cannot open the file.

Thanks for any insight!

Thank you Daniel.  Does what you say apply when people try to bring up a document assigned where the print queue is something like @notepad.exe or @write.exe (device type = DEFAULT)?


JDeTurk

Thank you Daniel.  Does what you say apply when people try to bring up a document assigned where the print queue is something like @notepad.exe or @write.exe (device type = DEFAULT)?


JDeTurk

Yes.

Thank you Daniel.  Does what you say apply when people try to bring up a document assigned where the print queue is something like @notepad.exe or @write.exe (device type = DEFAULT)?


JDeTurk

I probably should have added, that checking the file properties (with $fileproperties) of the print output file (returned in $result after the print statement) will only return something if the file actually exists. I'm not sure, but it is possible that the message frame could contain a "file not found" error in case of a failure, if $ioprint=64 is used. I did not test this.

Terms & ConditionsAccessibility statement