Developer Tool under Mac OS 10.2

[Piotr]

Has anybody been successful in using FM Developer Tool (v. 5.5) under the new Jaguar Mac OS 10.2? I tried it on 2 computers and neither the OS X nor the "classic" version works. They start up normally but unexpectedly quit half way through the process of generating standalone files (I tried with several different files.) I am preparing a commercial CD ROM based on FM and I am seriously considering doing it as a Windows-only product, I am having just too many problems with my Macs recently.

[rtyser]

I have had some success, though I've always experienced some crashes with the Developer Tool under OS X, both 10.15 and 10.2., though not under "classic."

Removing the FM preference files in my user Library folder eventually seems to get it back up and runnng.

Hope this helps,

Rob

[ottawadave]

Dumping the preferences does not help me get by this at all. I've had this problems with 3 databases on two machines and I can't seem to get by it all. Has anyone been able to build a standalone solution with FMP5.5 Dev on OS X 10.2.1 at all?

regards,

-Dave Villeneuve

[CG Software LLC]

I have created runtimes using Filemaker 5.5.2 under OS X 10.2.1. The application unexpectedly quits more than half the time and I have to run it again but I have been successful on occasions.

No problems under classic.

Regards,

Thomas

[ottawadave]

I had to clone a 10.1.5 install for someone today. Before I took the drive out I booted off of it and ran FMP Dev 5.5.2 from my partition and had no problems creating a runtime solution. In fact, the runtime solution ran fine after I'd booted back into Mac OS X 10.2.1.

So, I think the problem is definitely 10.2 related. Has anyone reported this to Filemaker? Again, I've not seen any hint of problems from documentation at www.filemaker.com

-Dave Villeneuve

[aersloat]

We have been able to bind solutions under Dev 5.5v2 and 10.2 but there have been some caveats. You can't drag and drop the solution files into the files window and we had to add "help" and "about" scripts.

Our bigger problem with 10.2 has to do with AppleScripting. For years we have been using a solution that we built to import and log digital photos that we take out in the field. The old solution file had been choking on import due to the .DS_Store files in OSX until we updated the scripts.

Now we have a FileMaker file that works perfectly-- all the scripts import just the way they are supposed to-- and we upgraded to FileMaker 6 Dev to bind it all up into a nice clean application. However, the new runtime does not work. It starts to execute the AppleScript step and then unexpectedly quits. In the process it mangles the solution file so that it will no longer open with the runtime (it requests to be "recovered").

We re-bound the solution with FileMaker 5.5 Dev and the runtime solution also does not work.

We talked to Filemaker tech support and they didn't really know. We have returned FM Dev 6 in the interim since the 30 day return window was closing for us. Tech support has copies of out crash logs, solution files, and system profiler reports. They were very honest about probably not being able to address the issue for a while.

It would seem to me that Developer has some problems with OSX 10.2 and AppleScript.

[bigfundj]

This is acknowledged at filemaker.com. The fix they advise is NOT to use drag-and-drop but to use the ADD button instead for adding files. Here's the catch -- if you EVER try/tried to use drag-and-drop you've corrupted your prefs for the binder tool. Go to your user preferences directory (Finder > new window > Home > Library > Preferences>) and find and delete the file called com.filemaker.Binder.plist.

Everything will then work correctly. Remember, NO DRAG AND DROP!

(OT: FMP 6.0v4 updater is out today on FM's FTP servers [look for the link on the downloads page for FTP] -- might fix the infamous "unexpectedly quit" problem when using FMP with CDML)

[CG Software LLC]

I've just upgraded to OS X 10.2.3 and now the Developer Tool unexpectedly quits every time I try to create a runtime. I only use the Add button and have deleted the com.filemaker.Binder.plist file.

Anyone have any other suggestions?

Why does FileMaker Inc take so long to get updates out for the Developer version? It costs more up front but support is much slower.

[kps]

I have just returned to the FileMaker community after an absence of a few years by purchasing FM Developer 6.

I am now experiencing the identical problem mentioned here. From the moment I installed FM Dev 6, I have never used the 'drag & drop' method to bind files and it always just 'unexpectedly quits' in OS X 10.2. Where is the fix? It should have been out by now.

I'm very, very disapointed with Filemaker Inc. right now.

[stefangs]

on the same subject, does anyone know if a solution that was bound under 10.1 with developer 6 runs stable under 10.2? that would affect my decision to upgrade to 10.2 at this point.

[webcat]

I tried to upgrade my new purchase of FMD6 with the downloadable upgrade to 6.04 but it won't work, says there is no FileMaker to upgrade!

is there something wrong or is the upgrade for FileMaker Pro and NOT FileMaker Developer?

[CobaltSky]

You're correct in guessing that the upgrade to 6.0.4 is for FMP not FMD.

I'm afraid that FMI is a lot quicker to publish updates for the desktop version, and the corresponding updates to the developer version are few and far between - if they arrive at all .

[After Hours]

All I can say is am I glad this forum is still around. Having developed many solutions in the past, then moving on to the web, I'm bringing some work back to FMD. And the Quit bug drove me bonkers tonight until I found your posts here.

FMI would do well to at least have a decent forum, or a link to this one, on their knowledgebase or support pages -- hours of wasted time there, and 15 minutes of answers which led to a solution of sorts here. thanks folks!

paul

[Pierre Igot]

I am, unfortunately, experiencing the exact same problem -- and it's driving me insane!

I cannot believe that a product that I paid $400 for doesn't even do the very thing I bought it for reliably!

Based on what I am reading, the bug has been around for a while. I've tried everything (deleting the various FMD prefs, adding custom About and Help layouts to my files, etc.) -- to no avail! Developer Tool still crashes for no reason -- or decides to work fine every once in a while.

I cannot believe this.

--

Pierre Igot

LATEXT - Literature & Visuals @ www.latext.com

BETALOGUE - Weblog at www.latext.com/blog/

"Apple Peel" Columnist @ Applelust.com

[deckard]

Has there been any resolution to this issue yet? I cannot downgrade to 10.1, nor did the "trash the .plist" plan work. Does FMI know about this?

[Onederdog]

I a'm using Filemaker 6 developer with OS 10.2 and the same crash during the bind process was happening to me also. I started to make a copy of the file I was binding on the desktop, then make sure filemaker developer is not running. Then start the developer tool and bind the file(s) like normal. The crash has not happened since.

Bruce

Onederdog Software

[alcam]

If I understand you correctly, you made a copy of your .fm5 file (File > Duplicate - or a duplicate from within FileMaker?) then proceeded with Developer Tool as normal. I just tried this and it didn't work. Still get "Unexpected Quit".

[davincho]

OK..i have the same problem with FMD6 (v6.03) with MacOS X 10.2.3 for my solution...But I tryed the next "solution":

Close you session and open in ROOT mode... then copy the databases and make you solution -NOT DRAG & DROP THE FILES, ADD THEM WITH THE BUTTON- (this work just fine for my)

[Skeptic]

I have been successfully building runtimes with FM Dev 5.5v2 for quite a while. I just updated to 10.2.8 and now when I go to build the runtime the Dev Tool is crashing.

I don't drag & drop the files, I use the add button.

Has anyone found a solution that actually works for this problem? There is no mention of this problem in the FileMaker support database, yet there are plenty of people here who have run into it.

Any assistance would be really appreciated.

Thanks

[kenneth2k1]

.8 just came out yesterday, didn't it?

I would maybe try reinstalling FM and updating. But FM still says that its requirements for FM6 are 10.1. Hahaha

FMI would probably tell you to buy the most recent version. That's usually their fix.

[Skeptic]

Yes, I stupidly updated my machine when software update showed up. I normally don't do it the first day... expecting it to be recalled--hahahhaha, like it was this time.... joke on me I guess.

Anyway, I did get it to build. I moved the files to the same hard drive as FM Dev Tool, I rebooted my machine (just in case), and it worked.

If it as stupid a bug as not being on the same hard drive... well, quality assurance at FileMaker should be embarrassed.

[kenneth2k1]

If anything, could you create the runtime in classic mode?

Does anyone know if OS9-bound solutions work in OSX? I've never tried it, but I could try it tomorrow.

[Skeptic]

That was going to be my next step, trying to build the runtime in classic. Of course, I wasn't sure if building in 9 would allow it to run native in X.

Luckily I got it running and was able to hand off the database to the person needing it.

[kenneth2k1]

Ok, I tried it, and it wanted to start with Classic. But I remembered that we don't have an OS9 volume on the drive.

So I conclude that it would want to start the runtime with classic, thereby not being able to run in OSX. In other words - no, you cannot run OS9-bound solutions on OSX.

Ken

[ruthcarlton]

I just downloaded the Filemaker Developer Update (6.04) and now I can build a runtime solution without Developer crashing in OS X 10.2.6

[Macs2u]

I had the same problem as you all with the Developer tool quitting partway. Had a hunch: I "recovered" the solution file (even though it had no fault) before I ran the Dev tool. It ran perfectly to create the Solution. Tried it again in case it was a fluke. Worked again perfectly.

So: "Recover" the file, (renaming the recovered file as needed) and then immediately create you Solution using the recovered file.

Let me know if that works! guy at macs2u co uk