Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

PDF Script in a multi-user OS X solution

Featured Replies

I'm familiar with the process for scripting PDF printing in OS X but this process doesn't work on a networked database. I've tried creating the same "PDF" preset on multiple machines but I get a printing error when anybody other than the host runs the script. Is there any way to script printing to PDF that everybody in the building can use?

What error do you get?

Ernst.

  • Author

"Sorry, Filemaker is unable to continue printing (Error -909)"

It is a bit of a shot in the dark, but you could try if it works if you

- specify the same (network) printer on both host and client, then

- open the print script in script editor and

- replace the 'page setup' settings after exiting the script edit window.

I'd be interested to know what happens.

Regards,

Ernst.

  • Author

When I use the client to replace 'page setup' settings, the host can no longer print with the 'PDF' preset. The host now gets the same error as the client did. I'm wondering if Filemaker is storing the exact path to the 'com.apple.print.custompresets.plist' file which is stored in the ~/library/preferences folder. If so, the stored path wouldn't work for a different user name.

Hey Kerver,

I tested it by defining a page setup and then loging in ith another user. Got the same error.

So I think you are suggesting in the right direction. Either the path to the preset, or the path for storing the pdf file, or both, might be causing havoc.

I'll do another test to rule out the second option.

Ernst.

I'm back.

I did the test by defining the path to save the .pdf file to, to a location (an extra harddisk) that is not specific for one user and I did NOT get the error.

You might try and see what happens if you define the path for the .pdf file to a server volume that's visible on all clients and the host. I think that will work.

Regards,

Ernst.

  • Author

Well at least we know the problem. Thank you for taking the time. Now I just have to figure out an elegant solution that won't burden the user with extra steps. I'll post my final results.

One suggestion would be to have the page setup step (which actually stores the data) in a single user file that is on each users computer.

I'd be happy to hear the results!

Good night,

Ernst.

If the page is printed from another file, this doesn't seem helpful. Page Setups are local to each file.

-Queue- said:

Page Setups are local to each file.

Hmmm, I'm affraid you are right.

  • Author

And using a set path on a server volume would erase other user's PDFs.

A -crappy- solution could be to make a small partition on every workstation just for pdf's.

  • Author

ernst said:

A -crappy- solution could be to make a small partition on every workstation just for pdf's.

You definitely hit the nail on the head with that one...it's crappy smile.gif. For now I think I'll direct the PDFs to the 'Shared' folder inside the 'Users' folder. This is a consistant path for everybody. Even if the HD is named differently it still works.

That sound like a better idea.

Anyway, problem -sort of- solved.

Regards,

Ernst.

Create an account or sign in to comment

Important Information

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

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.