Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

Best way - print has to be (but can't be) defined


This topic is 7211 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

I have a database set up to create invoices.

Page one must be on letterhead (tray 3), all other pages are to come from high capacity (tray 6).

I have set up the script to print page 1 to 1 to tray 3, and then print pages 2 to 9999 to tray 6.

My question is this - we have around 10 printers in the firm. If i create the script to specify pages to print, it obviously also specifies the printer. I want to use no dialog otherwise users will end up with 4 windows confirming print (page, printer, page, printer).

My initial idea for a solution is to create a layout with several buttons of all the various printers, get the user to select the printer they wish to print out to, then use parameters of the script (i.e if(printerselect = 1 print to laser 1) type scenario, which will mean I have to create 10 duplicates of the print command i.e

if(Get(ScriptParameter) = 1

      PrintSetup[restore]    [color:"red"]##print page 1 of 1 to tray 3[/color] 

      Print[restore]         [color:"red"]##print to laser 1[/color] 

      PrintSetup[restore]    [color:"red"]##print page 2 of 999 to tray 6[/color] 

      Print[restore]         [color:"red"]##print to laser 1[/color] 

else if(Get(ScriptParameter) = 2

      PrintSetup[restore]    [color:"red"]##print page 1 of 1 to tray 3[/color] 

      Print[restore]         [color:"red"]##print to laser 2[/color] 

      PrintSetup[restore]    [color:"red"]##print page 2 of 999 to tray 6[/color] 

      Print[restore]         [color:"red"]##print to laser 2[/color] 

and so on and so on.

OR is there a cleaner solution?

Posted

Above is correct but you are missing a change printer step. This is miserable in OS X but I think better in Windows, search the printer forum. If your users will always print from the same printer, but different based upon machine location or user, you could create a table that chooses the printer, eliminating the need for multiple buttons. Each user/machine would need to be configured only once.

Posted

Kiwiora,

I have a similar, but much less complex, problem and Queue kindly pointed out that FMP will only save one setting for PrintSetup/Print in a single script. You need a separate script for each printer.

I am printing up to 12 reports from one script and would like to use Print[no dialog] after the first report. The users use one printer 95% of the time but they need the facility to change it. They are quite used to changing the printer in the Print script step and I'd like to keep it that way rather then mess about with buttons.

Unfortunately, the only solution I can see is to use buttons or a custom dialogue- and multiple @**^!%~#@! scripts.

Posted

It does, but there is also a bug when using Print [No dialog] that may cause you problems.

Posted

accckkkkk

Ok so what is the final judgment - I do need a separate script for each individual printer? (i.e 7 near identical scripts ick)

The scenario becomes worse with my other new database (busy). Firstly, I have different label sizes (Sml, Med, Lge, XLge) I first need to go to the appropriate "size" layout and print that portrait then go to layout 2 and print that landscape.

So what's that???

Select printer (button)

go to layout (sml med lge)

change to landscape

print

go to layout (page)

change to portrait

print

x 10

Why couldn't they design a "page setup" much like word or excel that is independant of printer selection!!!

dkemme - couldn't find the technique you refer to B)

This topic is 7211 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.