I gotta agree with Maerix and his complaints about this one. And it's not just because I've been going back and forth with him trying to get both of our projects from crashing. I think FileMaker has SOMETHING wrong with it: not sure what, but something. FileMaker told him his FileMaker files were corrupt. If that were the case, one would assume the database files would not matter if they were run on a PC or a Mac. Well, him & I experienced problems ONLY on a PC. Ran PERFECTLY on a Mac. So there has to be something to that.
As far as limitations, it really sounds like there are some to it. Granted, if you are an experienced FMaker user, you can easily get around them by breaking files up, etc. I don't know about you guys, but I first started using FileMaker building my project. And I've grown and learned about it as the popularity of my solution has grown, causing me to add to it. Unfortunately, rewriting and splitting up my project is not as easy as copying and pasting code to another file, unless somebody has a way to copy fields & layouts easily. For people like us who started learning & writing databases at the same time, we are in an unfortunate position.
I am going to start a rewrite of one of my apps down the line, and unfortunately, FileMaker is not going to be used. I am playing around with Visual Basic, ActiveX Direct Objects, and Microsoft's Jet engine (access files). I love the speed of development in FMaker, but you lose raw power. The unability to run a script when you leave a field, tabbing to buttons, customized shortcut keys (besides leaving stuff in Scripts), inability to really communicate with other Windows programs, and the poor method of upgrading multiple databases at once is a big turnoff when you are trying to sell a "professional" package. It's funny, FileMaker has been around forever. You would think they would address a few of these issues.
My frustrated $.02. :-)
Eric