dshafer

quote: Originally posted by BobWeaver: Let the nerds that need to have the bleeding edge software go through the misery of debugging it. While I don't take issue with the underlying advice of waiting a while (a year was what was suggested) before adopting a new OS, it was unfair of you, Bob, to suggest that only "nerds who need to have the bleeding edge software" should move to OS X at this point. OS 9 is unstable in too many situations. I'm a power user but I don't think I'm an OS nerd. I just got really tired of rebooting OS 9 every time Word crapped out trying to print or Eudora hung up trying to get mail. I moved to OS X about 10 days ago now and I spend all day in it. I still have to use OS 9 occasionally (e.g., for FileMaker Pro, where there are still too many reports of bugs) but I would never go back. To see why, read my Weblog (http://radio.weblogs.com/0001285/) articles. It may not be for everyone, but it's moved well beyond the nerds-only stage!

Well, none of those restrictions applies here. I am not using MAC OS security. No log-on password. No Web or other server active. I did not rename the file; I just recently instlled FMPro 5.5 cleanly (i.e., not an upgrade). It's not the developer edition. I remain bewildered.

Still no joy. It updates the application correctly (or appears to) but with 39 of 41 files remaining to install, it quits with the error I reported earlier when it appears to be trying to update "Read Me." Read Me is there. I've tried renaming and deleting/removing that file from my 5.5 folder. No luck. Has *anyone* gotten this upgrade to install correctly on 9.1 and 5.5v1?

Interesting. The Windows version of CHP seems still to be online but the Mac version, at least when I attempt to download it through download.cnet.com, doesn't work. No such file.

Thanks, Jim. But I don't have FMD so that's not the issue. I *do* have a copy of FileMaker 4.1 on the drive, so I'm going to try copying it to another machine temporarily and deleting it from this one and see if that works.

Well, it appears to me from a couple of hours of testing that some CDML stuff still works in 5.5, but some doesn't. For example, tags that are designed to include other files do not appear to work. Perhaps the syntax has changed. But at least it doesn't appear that all is lost. More learning to do.

Thanks for the clarification, "Bridge"! I did a search at FileMaker.com but apparently didn't look far or deep enough. I'm going to see how this stuff works starting off assuming it *will* work this time. Maybe most of my faith in FileMaker will be restored after all.

I can't tell if the update completes. It *appears* to me that the application itself upgrades correctly (there is a FileMaker Pro.old in the folder along with a new FileMaker Pro), BUT the install quits with 40 files yet to move according to the progress dialog. It's a local CPU, so there's no password control at issue.

Thanks, Anatoli. Wow, I always admired FileMaker as a company that paid attention to its customers and did a better-than-average job of creating new value with revisions. This is a MAJOR step backward. I am now going to have to uninstall 5.5, return it for a refund and then order FMD 5.5 to get custom web publishing capabilities. That's a horrific decision on their part. And, of course, there's no way to register a complaint that gets heard and responded to at FileMaker.com; they give you a feedback form but they all but guarantee they won't respond to your comments. Sad.

Running Mac OS9.1 upgrading FMPro 5.5v1 to 5.5v2 with the FM updater. It appears to update the app correctly, creating a file called FileMaker Pro.old and a new FileMaker icon appears but then it stops and says, "An error prevented the update from completing. Invalid file selected for updating." Huh? The next dialog gives an error code to boot: 11002:2,-14. Help! [ December 23, 2001: Message edited by: Dan Shafer ]

I recently upgraded from FMP4.1 to FMP5.5. I just went to work on some ideas for a FileMaker-centric Web page I wanted to build (allegedly improved Web publishing was one of the reasons I upgraded). I find that unless I'm missing something, there is no support or documentation in 5.5 for custom Web publishing at all. In other words, FileMaker decided to DELETE from an UPGRADE a valuable and useful feature of their earlier product. Tell me I'm wrong. Tell me I'm blind. Tell me I'm missing something. But don't tell me these guys could be this stupid.

Thanks for the advice, Bob. I'll try to get that working. This whole thing with having to connect to a "remote" database on the same LAN and how FMP thinks about "hosting" is a little out of kilter with the reality of a networked world, but I'm getting a handle on it. I think.

Sorry to bother the list with this one. Sheesh. I had the protocols set to TCP/IP in one place and AppleTalk in the other. As soon as I got them both talking AppleTalk, all was well. Thing is, I didn't set this in either place, so it appears FM did this at install time and did it differently both places. Anyway, it's working now. I knew this had to be easy!

I just upgraded our databases from 4.1 to 5.5 and installed one new and one upgraded 5.5 on the LAN. We use AirPort to network. The main machine has the FP5 files on it. The folder in which the files are stored is shared with the other computers on the network. When a machine on the net shares this folder with my main system, it can see the files in the folder just fine. All of the files are marked multi-user and not hidden and all are sharing over TCP/IP. But any attempt to open a file which is already open on the other machine results in an error saying the file is single-user or the host can't be found on the network. Clearly the host is found; it's sharing the file via AppleShare just fine! Clearly, the files are multi-user; I've triple-checked that. The lock problem goes both ways. If the file is opened first on the other machine, I can't open it. If I open it first, they can't open it. So what's going on here? What am I missing about this easy file sharing stuff? I've been using and programming Macs a long, long time (maybe too long?) and this is the first I've run into a problem with AppleShare sharing files over an AirPort LAN. [ December 18, 2001: Message edited by: Dan Shafer ]

Thanks for the clarification. It's (almost) always a nice day in Monterey!