Hi,

I have a strange problem. I have a script whose end result it is to print a report. It is working fine in the developer computer.

The solution is deployed in a Windows 2003/Windows XP TCP/IP network.

However, in client computers where the default printer is different from the default printer in the developer computer, the script runs fine until it reaches the point where the user press the OK button to print (printer selection dialog, Print step in the script). When the button is pressed, the computer reboots. This happens in every computer in the network in which the default printer is different from the developers default printer.

This only happens if the user does not change the printer from the default printer to the printer originally assigned to the script in the developer machine. If the user changes the printer, the script runs fine.

Initially I scripted the printer selection, but I had to remove it because of this issue. At the moment, the only print step present is Print, allowing user interaction with the print dialog. After this step, the only steps are Close window > Commit Records request > Exit script.

It is not a driver issue. All other programs in every networked computer print fine, whether from the default printer or any other printer available in the network.

Even FM prints fine if the other printer is manually selected, but not if it is scripted.

Any lights on this issue? Must I use a printer selection plugin as the only viable alternative?

The printer drivers are the latest available (both printers are HP, one colour, one B&W)

Thanks

Edited December 14, 200718 yr by Guest

I have the same problem. Try putting a 3 second delay after the print set up script and see if that helps. This seems to work for me.

Thank you.

That seems to solve the issue (at least in my trials).

If it is a bug (as it seems it is), I hope the guys from FM solve it in the next patch.

Thanks again