For better control of the printing process, you might consider using the MyFMButler plugin.
To work around such issues, I sometimes set up a "print" script that does not print anything. It pulls up the correct found set, enters Preview mode and pauses. In preview mode, wrong paper sizes or print orientations are usually quite visible.
To print, the user then selects print from the File menu like they would any other application and can then select the print and printer set up options that they need in order to print successfully.
The down side to this option is that you may need to teach your users the difference between "records being browsed" and "Current Record".
Well. . . I don't remember needing a plugin or work around for this is the last couple of Filemaker versions. In fact, I remember a local developer (a member of the Richmond XMug chapter) expressing relief when this was "finally" solved in either FMP 10 or 11. I was using multiple printers then, and never had the problem after upgrading.
While your interim scrip will alert users to the issue, it's still an interruption, and these are not highly skilled FM users. The other thing is that the setting for the label printer include specific "page, or label" size, intensity, margins, etc, all set in the driver interface.
My issue with the plugin solution is that I'm working on a very large corporate network, and everything is tightly controlled and vetted by the IT group before allowing installation on any computer (we are still trying to update to FMP 12 v4). This problem has significantly cut into the efficiency factor of FMP in our work flow.
Are these really the only solutions? And why can't the script remember what it is set for, anyway? What is the point of including Print Setup in the script if it can't remember it?
Not meaning to rant here, I'm just pushing a bit before giving in to a plugin to fix something that seems surmountable natively.
Say it ain't so! (is it possible that v4 will fix this?)
FileMaker has always been a bit hit or miss when it comes to printer interaction. I've always thought that this was due, in part, to the fact that the code needed to generate a print job file in FileMaker is quite a bit more complex than that from most other applications. Whether that is true or not, it has always been a potential issue for specific printers (or more precisely, certain printer drivers) that fail to "play nice" with specific version/OS combinations of FileMaker. I've tended to use this Preview/Pause method as an effective method that has avoided a lot of issues in getting solutions to work with particular printers.
While your interim scrip will alert users to the issue, it's still an interruption, and these are not highly skilled FM users.
Yes, but this often does not require a high degree of skill on the part of the users. The system requires them to use what for most computer users is a very familiar method for printing from just about any computer software. And it is often possible to resolve the "records being browsed vs. current record" issue by telling the users to always select "Records being browsed" and then designing the preview script to isolate the current record in a found set of a single record whenever the report is intended to only print the data from the layout's current record.
Another thing that you can try is to run an Advanced Options Recover on a copy of your file and test the recovered copy to see if you get any change. Select these Advanced Recover options:
Copy File Blocks As-Is.
Delete cached settings
These will reset a few things that can affect printer operation back to "factor spec" and that, once in a great while, can fix a printer issue.
Thanks, Phil, for your last post.
I did some web research this morning on this issue, some of it leading back to other posts on this forum, and I'm convinced that short of a plug in, work arounds are it.
My previous experience was with a Mac, so this may have been the reason the scripts ignored any previous printer. One last thing I'll try is to set the default printer (OS level) to one I never use, just to see what happens.