I converted our databases from FM 4 to 9 recently, but have noticed a problem with the scripts. I've modified the print options and even print setup within any script, then exit the script and return, my changes are gone. Regardless if I use a dialog window or not, it will print to whatever the last setting was in the computer's printer settings rather than what the database script is calling for.

Ex: If I print something outside of filemaker on a letter sized paper, then return to filemaker to print an envelope, the envelope prints on letter sized paper rather than what the script is telling it to: which is #10 envelope. This is particularly annoying when it defaults to print a "current record" on a list, say for a catalog, rather than the "found set." My work around is to have users choose the print options rather than allowing filemaker to determine--but we can't have it this way...

You have specified the Print Setup and Print options within those script steps? It's not like FM4, where the script "remembers" the settings. You need to use the script steps explicitly.

Also, I would create subscripts for printing, PrintCurrent_Portrait, PrintRange_Portrait, etc. and call those in your report script.

Yes, the print options and setups are actual script steps. I also created print subscripts to see if that would work--printcurrentrecord, printenvelope, etc.

Regardless if I took the "show dialog" part of either print options or setups script steps, each computer would default to whatever tray or printer it printed last--and each computer is different. One computer that printed last to tray 2 would print any print script to that tray--regardless of what the script says, one that printed last to tray 3 would print any print script to tray 3 and so on.

Well, now that we have that out of the way, I regret to inform you that this is a known bug. On another forum, Rick Kalman, Sr. Mgr. Desktop Products for Filemaker Inc. said in reply to a complaint about Print Setup Restore not working, "We are aware of this issue, we are working on this issue, and we will address this issue." (March 6, 2008)

Well, thank goodness it's not me then! I'll keep my eyes open for a fix in the future! Thank you for your help!

It's not you. I know how you feel. Believe me you're not alone. See FM Knowledgebase Article #6335.