John, Do a Google search for: "filemaker printer selector plugin" and you'll see several plugins which address this issue.
-- Steve Gerow FileMaker 9/8/7 Certified Developer President Abrazos Data Consulting, Inc. Pasadena, California Member FileMaker Bus. Alliance > -------Original Message------- > From: John French <[email protected]> > To: [email protected] > Subject: Choosing a printer ... permanently > Sent: Mar 10 '10 18:58 > > >>... I change the printer, and it remains the "default" as long as > >>the database remains open. However, when I close the database and > >>reopen it later, the original printer is back in the default > >>status.... > > > >Page setup options can be saved/restored in your FileMaker > >databases. Bu the default printer is a function of your operating > >system, not FileMaker. > > Ah, would that it were so. I do, indeed, have Printer A set as the > system-wide default printer in System Preferences|Print & Fax; and, > sure enough, every application and document in the system seems to > recognize that and aims at Printer A by default... > > ... with a single exception. There is one FMP database that has > somehow gotten pointed to Printer B as its default, and no amount of > changing the printer within the database nor in System Preferences > will change that with anything resembling permanence. > > So, my question really boils down to: how can I get a specific FMP > database to recognize that it should point to the system default > device, Printer A, not Printer B, whenever I open it? In case it > helps, I have also noticed that this particular database always opens > to a specific record in a specific layout, no matter what record was > being browsed in what layout when I last closed the database. IOW, > the database seems to have frozen its startup state, no matter how I > leave it. > > Also, FWIW, there are no scripts defined for the problematic > database, so I'm pretty sure that nothing unseen is going on in the > background which might create the apparent startup state. All other > FileMaker operations appear to function without any problem in this > database, and all other FMP databases behave themselves quite > satisfactorily. > > All references to FMP are FileMaker Pro Advanced 10.0v3; and the > operating system is Mac OS X 10.5.8. > > Cures? Ideas? Please. > > Thanks, > John French >
