rtyser

Has anyone tried FileMaker with the OS 10.2.1 update to see if some of the bugs reported here and in the Filemaker Products/FileMakerPro 6 discussion have disappeared? Rob

Thanks. Your suggestion is a useful work-around until this bug is corrected. Rob

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

One of the other posts here notes a similar problem that I have encountered with FM 6.0 and 5.5 when running Mac OS 10.2. This problem did not occur under 10.15. Unless the FM application is already running, FM files that are password-protected do not open when they are double-clicked. These files *do* open if they are not password-protected or if FM is already running. This bug persisted even when I did a complete reinstall of OS 10.2 -- wiped the hard drive clean, etc. Can anyone else confirm this bug? Thanks, Rob

Thanks for the reply. The "developer tool" is really the only thing that crashes. I did put the latest update (v2) on my machine. My feeling is that it is just a bit buggy. I've had crashes on 10.15 as well as 10.2. Take care, Rob

Thanks for the alias suggestion. I actually tried using an alias approach. However, the alias pathname on my computer did not work when downloaded to another computer. Is there a way to use a "relative pathname" (or some other trick) to get the same alias to work when downloaded to different machines? Thanks, Rob

I've been using FM Developer 5.5 for several months under Mac OS 10.15 and now under 10.2. Unfortunately, I experience fairly regular crashes when using the Developer Tool to make runtime solutions. For 10.2, I wiped my hard drive clean and did fresh installs of FM 5.5, and still experience periodic crashes. After a crash, I trash all of the FileMaker-related preference files, restart, and eventually crashes disappear for a while. I've attached a crash log on the outside chance that someone might be able to interpret what is going on. Thanks.

I'm making a cross-platorm runtime solution. Things work pretty will, but the PC runtime solution folder includes (1) the runtime engine = good, (2) the target file = good, and (3) many .dll files =bad. In otherwords, the PC user experience is awkward becuase she/he must view all of the .dll files. I distribute the PC soluction with these files tagged as "hidden", but unless the user has the "Do not display hidden files" option checked for their folder properties they will see all of these darned .dll files. Is there an obvious solution to this problem? Thanks, Rob

I have found another bug that may be related to this one. Under Jaguar, clicking on a password-protected file doesn't open the file unless FM is already running. If the file is not password-protected (or if FM is already running) the file opens all right.