Pages Blank in OS X - Perfect in OS 9

[vr5150]

I switched to os x from os 9 and now most of the pages in my database print blank, but if I print the same page in os 9 is works perfect.

I have manually printed and used scripts no difference.

I created a new database and it printed fine and i then copied some of my layouts from old to new and they would not print either.

You would think Apple would get off their butts and fix printing problems with OS X since they tout it as the best ever OS and it is but simple things like printing keep many from making the switch.

UPDATE I tried it in FMP 5.5 and FMP 6.0 same results.

[harryk]

What does your Preview in Filemaker display? Is that all right?

[vr5150]

In Preview everything is there.

[harryk]

>Preview is fine

I have not a clue, work myself still in OS 9. Seems a ******* frustrating problem.

[color:"red"] Hope for you OS X users take the trouble reacting [color:"black"]

[keshalyi]

What kind of printer is it? From the sounds of it, Filemaker is producing the right information, but its not translating through the driver to the printer. I'd look at more issues with the printer: try downloading the newest drivers, etc. Also, try printing to an EPS or PDF, see if it comes out. If so, can you print the EPS? Not a good solution to the problem, of course, but it might give some clues as to how to fix it?

[danjacoby]

Check the Apple website for OSX upgrades/fixes. Printing is a bit of a problem with OSX since they switched to a PDF engine. I would like to think they've fixed it by now, but since I don't use OSX (yet), I don't know.

It's almost definitely an OSX problem, though. If downloading a bug fix doesn't do the trick, I suggest contacting Apple.

[kenseye]

I'd stay away from running FMP in OSX, I'm still running in classic as even FMP6 still does not have full funtionality in OSX. Classic has not been a problem, even printing to a networked inkjet. OSX has no driver for an ethernet injet on print server.

[keshalyi]

WEll, YMMV, of course, but I've been test-running my db which is up to its ears in postcripting issues, on an OS X network at home, and I've had nary a problem with it. Don't rule out a problem with the setup of your printer. Still, YMMV, it may just be that your printer doesn't want to play nice yet. Yet another good argument for buying PS native printers...

[mgeorge]

I had a smilar problem in FM 5.5 under OSX. It turned out the the PS font used in the layout was an old one and the printer component of the font wasn't being sent to the LaserWriter. Changed the typeface - converted it to TrueType - and the problem went away. Other postscript fonts printed just fine.

Mike

[hatmaker]

I have had the same problem as described above. I have a layout that will print fine in OS 9, but in OSX it will not print. I have tried it on two different printers (one a laser printer, the other an Epson inkjet) with the same outcome. I even tried creating a new layout and printing the desired fields, but the new layout would not print. I did not check the fonts, but I am going to and will let everyone know if that fixes my problem.

Terry

[Oyseka]

My problem with blank pages is slightly different in that it is only when printing a page range from a found set that they are blank. When previewed in Acrobat all of the pages untill the end of the range are shown with the earlier pages before the range required being blank,

[Bob White]

I'm using FMP 6 and OSX 10.2.5 currently. When I upgraded to 5.5 and an older version of OSX, I had this problem with several TrueType fonts. If those particular fonts were present in a layout, I would print a blank page. If I changed the font, the page would print just fine. As you may or may not know, you can store fonts practically anywhere in OSX. By trial and error, I finally figured out that that the guilty fonts were stored in HD>Users>UserName>Library>Fonts. I moved them to HD>System>Fonts and the layouts starting printing just fine. It drove me nuts for a couple weeks.

I have run into this problem with several other applications. My theory is that there are driver programmers out there that aren't up to speed on OSX and are still looking for fonts at HD>SystemFolder>Fonts as with previous versions of the MacOS.