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.

OS X bind buggy?

Rob P
in Developer Tools

Featured Replies

I just bound a solution on OS X 10.4.6 using Adv 8.3 and the solution crashes on startup. Anyone have similar issues? Does anyone have suggestions?

Try updating the OS. Latest is 10.4.8

If your on an Intel Mac then you must upgrade FM to 8.5 as FM states NO SUPPORT for ROSETTA.

  • Author

Sorry, I am running 10.4.8. I've got a Dual G4 1.25 GHz with 1 Gb RAM.

I tried a bind on XP using 8.5 Adv and it works fine. But of course, I need a Mac version.

  • Author

I've upgraded to 8.5 ADV and still have the same results. Anyone?

Take the solution to another Mac and see what happens. If you don't have another machine then I'll test it for you (or maybe others). I know that the download will be large (50Mb), so you'll need to post an ftp address where it can be downloaded.

HTH

  • 3 weeks later...

I do not know the details but my tech support guys tell me that 10.4.6 was a "bad" update from Apple.

Why not try updating to 10.4.8 and then re-installing Filemaker?

Have you tried reparing permissions or doing more common repairs on your system?

It's seems silly but worth a stab.

  • 1 month later...

I have the same problem.

I'm using FileMaker Advanced version 8.0 and 8.5, and the same thing happens either way.

I make the runtime app, and I can run the application once. From there on out, the runtime app just refuses to launch. It bounces once in the dock and quits.

I'm running 10.4.8 on both my machine and another test machine. My test machine is virtually a clean install of OS X, I'm pretty sure that's not it. What could be causing the runtime to quit starting up after the first time? Frustrating!

FileMaker's knowledgebase has a very brief article that says this behavior should have been fixed in 8.5, but obviously it hasn't been yet.

http://filemaker.custhelp.com/cgi-bin/filemaker.cfg/php/enduser/std_adp.php?p_faqid=6131&p_created=1152572921&p_sid=2WZx-hri&p_accessibility=0&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9NzY2JnBfcHJvZHM9MCZwX2NhdHM9JnBfcHY9JnBfY3Y9JnBfc2VhcmNoX3R5cGU9YW5zd2Vycy5zZWFyY2hfbmwmcF9wYWdlPTEmcF9zZWFyY2hfdGV4dD1tYWMgcnVudGltZSBkb2Nr&p_li=&p_topview=1

Create an account or sign in to comment

https://fmforums.com/topic/47547-os-x-bind-buggy/
Go to topic listing

Important Information

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

I accept

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.