|
FileMaker Pro 7 |  | From: Filemaker Inc.
Category: Software
List Price: $299.99
Buy New: $265.00
as of 7/29/2010 18:06 EDT details
You Save: $34.99 (12%)
New (2) Used (4) from $169.00
Seller: Shaker_books
Rating:  9 reviews
Sales Rank: 4940
Format: CD-ROM
Platforms: Windows 2000, Windows XP
Media: CD-ROM
Edition: Standard
Autographed: No
Memorabilia: No
Operating System: Windows XP
Shipping Weight (lbs): 4
Dimensions (in): 3.7 x 3.2 x 0.8
MPN: F100CW00U
Model: F100CW00U
UPC: 044866023308
EAN: 0044866023308
ASIN: B0001LUH9M
Release Date: March 13, 2004
Availability: Usually ships in 1-2 business days
| |
| Features:
| • | Track and manage people, projects, images, and data | | • | Do more, faster with 30 starter solutions | | • | Exchange data with a virtually limitless number of applications | | • | Store, track, and archive files and documents | | • | Secure data with assigned accounts and privileges |
| |
| Editorial Reviews:
Product Description
FileMaker Pro 7 is a revamped version of the already-powerful database tool. The newest version of this database tool has enhanced relational capabilities, easier integration with enterprise databases, and deeper security. Combined with support for new file formats and other development tools, it's a new way of organizing data, according to your needs!
|
| Customer Reviews:
Showing reviews 1-5 of 9
 The app I use most and teach others how to use... April 27, 2005
No Vitriol Here (San Francisco)
34 out of 35 found this review helpful
A good deal of what people have written about this product simply isn't true, particularly negative observations such as not being able to import/export or that security is non-existent. Why people with only cursory knowledge speak with such authority has always puzzled me. So I offer an objective, if lengthy, review.
I've been using FileMaker since 1990. Developing FileMaker applications has been my primary source of income for almost as long. I develop in Mac OS X (Virtual PC with Windows 2000 Pro for testing). I've also tech edited an upcoming advanced book on FileMaker 7.
Version 7 is a huge upgrade over 6 (I'd call it a 'crossgrade', as in switching to similar but different product). As such, converting solutions from 6 to 7 can get really hairy, and it may be that a complete re-write is more efficient. That said, many FileMaker solutions that people have developed or inherited over the years weren't written following "correct" database rules (this is why IT types hate FileMaker), so a re-write may be a good thing. Generally, an upgrade to 7 is brought about by a need for larger file sizes, to increase the number of simultaneously open files or to consolidate data. If you've got a solution that works fine in 6 or earlier and you're not a developer, I'd think two or three times about upgrading; it's not something you want to do for the sake of it.
For users, that is people who enter data, the changes in 7 aren't apparent. It's the back end, for us developers, where the changes are significant, plentiful, and very welcome. If you're just getting started in the world of FileMaker, forget all about any earlier versions. The rules have changed in 7, and it's almost more difficult to unlearn what you know from 6 than to start fresh in 7.
FileMaker has a scalar learning curve. That is, it's easy to learn and get up and running in really no time at all (and there are plenty of free sample files to take apart and learn from). As your database becomes larger, more complex and gains a need for multiple simultaneous users or interaction with other systems, knowing the normalized rules of relational database structures becomes increasingly important, and that's where the learning curve steepens. But don't let anyone fool you, this is true of *any* database development software.
Building a database is a lot like being the architect of a building. You have to have a good idea of what it's going to look like in the end, before you start. For example, if you know your one-story house is one day going to be a 4-story mansion, you want to have a good foundation. If you know you might want the ability to relocate a bathroom to the other side of a floor, you've got to build in some room at least for plumbing, electricity, maybe some windows. It's not a realistic analogy, but it usually helps people understand the thinking involved around creating a database.
I firmly believe FileMaker is the easiest of any to learn, use and maintain, that can also handle whatever complexity you throw at it. Further, it's cross-platform and things like networking your databases and making structural changes (even remotely, without bringing down the system) are really a breeze compared to programs like Access.
Lastly, one of the neatest things about FileMaker is its developer community, which is today thriving and strong. Almost like an open-source coummunity, we seem to really enjoy helping solve each other's problems (no one person knows everything about FileMaker, even at FileMaker, Inc), so we're always learning. There's plenty of free community support available that, I've found, is often better than the company's own tech support, although the folks at FileMaker are really great and genuinely into supporting the developer community. And...there's plenty of money to be made as a FileMaker developer the world over. We're certainly in demand and have been going strong for nearly two decades.
You can read FileMaker's feature list to find out about all the new features. Here are my likes and dislikes:
What I like most about 7:
* Multiple tables in one file (with an 8 terabyte limit per file; formerly 2GB).
* Multiple windows from the same file, and the ability to manage their placement dynamically, down to the pixel.
* The ability to separate data from logic (for example, keep your data in one file, and all your scripts and interface elements in another...changes and solution upgrades to your clients are much easier to facilitate this way).
* Much improved security and account management (that supposedly plays well in authenticated corporate environments...I'm just getting started in this area).
* The ability to use PNG images with transparency, which greatly improves what you can do with your interface.
What I DON'T like about 7:
* All my complaints boil down to FileMaker's interface. I strongly believe a complete overhaul is way overdue (if it were like Omni Graffle, I'd be in heaven). There are plenty of little annoyances because I use a Mac. For example, I have a Microsoft 5-button optical mouse. The scroll wheel, which works in every single application (even on FileMaker for Windows using Virtual PC on my G5), doesn't work at all in FileMaker for OS X. This is ironic because FileMaker is wholly owned by Apple, but development for the Mac seems have been an afterthought. Much of this will change in the next version, just around the corner. I wouldn't dream of developing primarily in Windows, largely because of the way Windows OS handles windows and value lists within FileMaker; you have less room to work with.
* The relationships graph, which sort of looks like an ER (entity relationship) diagram but is not, can get messy very quickly, and they've taken away the ability to look at relationships in a straight text list (I'd like both). This can get frustrating, especially if you've inherited someone else's mess. The fact that FileMaker has implemented a certification program for developers, and is working actively on releasing development standards will help reduce confusion and frustration in this area.
* The inability to move tables, fields, script steps, etc. from one table or file to another. Improvements in this area are expected in the next version.
* The inability to see how elements are related to each other. For example, it's not possible to see all the elements that call a script (i.e. a parent script or button, etc.). There are software tools that can analyze FileMaker files and expose this information, and they work great, but it would be nice if it were integrated into the program itself.
* It's a minor complaint, but worth addressing here: A number of things don't work like you'd expect or want them to, so you have to create workarounds. This appeals to the geek in me; I usually like the challenge, but sometimes it's frustrating because you'll think it's silly that something simply doesn't work like you want. That said, over the years there is nothing, really nothing in terms of complexity that I have not been able to achieve with FileMaker by itself or with the help of a plug-in. People ask me "Is it possible in FileMaker to..." I always answer yes before they're finished. It's sometimes a "Yes, but..." answer. For the snotty programmer types, I challenge anyone to name database development software that is impervious to workarounds, OR that does not have a high learning curve. If you don't have a background in databases, FileMaker is a great path. If you do have such a background, open your mind and you'll find that no, FileMaker is not the end-all-be-all database app (such an app doesn't exist), but it really is a neat and productive tool, and if you can build good solutions that manage your client's data, they will loyally worship you.
 FileMaker Quirks January 11, 2005
Tech Reviewer (San Diego, CA USA)
24 out of 30 found this review helpful
FileMaker is perhaps the easiest application to use for creating a simple database. But, there are a few quirks about this software that really bug me:
1. Danger of storing layouts, scripts, and data in the same file
Layouts and scripts are stored in the same file as the data. If FileMaker crashes while editing a layout or modifying a script, the whole file including the data may become corrupt and unaccessible. A better design, in my opinion, would be to keep the data separate from the layouts and scripts, so the data would be protected in an event of a crash.
2. Danger of linking to wrong external relational files
Filemaker links to externally related files by an unusual search algorithm. If there exists copies of files with the same file name on the server, on the local hard disk, or hosted on other hosts, then which file is linked becomes ambiguous. The wrong external file may be linked.
3. Danger of opening the wrong file
Each Filemaker application can host files. If a user were to host a file that has the same name as a file hosted on the server, other users may open the wrong file.
4. Danger of deleting your entire database
The "Delete All Records..." option is one of the most dangerous features of FileMaker. Many databases were wiped out because a user accidently chose the "Delete All Records..." rather than the "Delete Record..." option -- the two options are placed next to each other in the menu, inviting disaster.
5. Cumbersome queries
The querying feature of FileMake can be a pain to use. To create a query such as (Field1 = "criterion1" and (Field2 = "criterion2" or Field3 = "criterion3" or FieldN = "criterionN")), FileMaker requires you to break down the above query as N-1 queries: (Field1 = "criterion1" and Field2="criterion2"), new query (Field1 = "criterion1" and Field3 = "criterion3"), ..., new query (Field1 = "criterion1" and FieldN = "criterionN"). There are other queries that can be easily posed as a SQL statement but not so easily done in FileMaker.
6. Spaghetti code paradigm
Variables for your scripts in FileMaker are stored in global fields. You'll have to keep track of which scripts are using what global fields -- the script and the variables are not kept together. Passing parameters to scripts is a cumbersome sequence of setting the global fields one-by-one, then calling the script. Most modern programming languages have procedures with calling convention such as p(x,y). In FileMaker it's set x, set y, perform p. To debug, you'll have to read the code of p to see that p really references x and y. Also, their is no hierarchy or encapsulation of scripts, so you'll have to devise your own way for organizing.
Filemaker Pro for the novice November 17, 2004
Roxanne (Greece)
18 out of 18 found this review helpful
As a novice user, with practically no knowledge of computer programming and scripting, I would like to say that Filemaker is one of the easiest databases I have ever used. I started out using Filemaker4 - this had its limitations, but the fact that I could easily and efforlessly create a whole database with functional buttons and easy links to other layouts was so great!
It is relatively foolproof for those who do not wish to overload their minds with programming data that they will probably never use (and they only need to pay the cost of the package instead of the programmers they would probably need to employ in order to keep their database up and running flawlessly; with no disrespect to you programmers out there - I wish I could BEGIN to understand the way it all works, but some of us are not blessed with the time or technological knowhow that some take for granted - but I do understand why you are frustrated by the simplicity - remember that for those who need it, Filemaker does the basic database job, in a more simplified manner).
I give 4 stars because, although user friendly, there are annoying limitations that have been noted before - ie: multiple layouts for manual change each time IS annoying, auto saving with no "undo" option is dangerous for larger databases etc.
In summary, I feel that Filemaker is an excellent ready-prepared database solution for any individual or business that requires the "quick-fix" Filemaker offers so easily.
Not perfect, but FM7 offers many long-awaited features November 6, 2004
R. W. Mercer (Florida)
24 out of 24 found this review helpful
FileMaker 7 is a very fast and reliable rapid-application-development package for both Windows and Macintosh. With it, you can create single- and multi-user databases quickly and easily without programming or advanced training. You can start with a single-user system, and if your needs grow, you can then scale up effortlessly to a server-based platform with up to 250 users.
FileMaker is "high level", meaning you don't need a deep understanding of underlying data structures and theory to do useful work. This makes it ideal for smaller organizations who can't afford the expense of a full-time administrator/programmer, but still need a reliable, powerful, multi-user database.
If your ideal database environment includes Oracle or Crystal Reports, FileMaker is probably not for you. FileMaker simplifies things. There are only a handful of data types, only a few types of controls. In fact, experienced DBAs are often baffled by FileMaker's simplicity. But FileMaker can do very complex tasks with its streamlined approach.
Experienced FileMaker developers will find most (but not all) of their pet peeves have been eliminated with this version. Many long-standing limitations are now gone.
Despite some absurd claims to the contrary, Version 7 continues the long FileMaker tradition of importing and exporting a variety of data file formats.
The once-pathetic ODBC drivers are dramatically improved, and are now actually useful. JDBC is also available this time around, though emphasis appears to be on XML for the future. The Web Publishing feature is now XML-based, a welcome change for integration with other database platforms.
Additional FM7 advancements:
- Multi-table files and improved relationship management with multi-field keys.
- Elimination of restrictive file and field size limits.
- Editable finding and sorting in scripts
- Linguistic indexing has been expanded from the old 20 characters-per-word limit to 110 characters per word.
- User definable functions with recursion (my favorite)
- Encryption support for both native and web-based networking
- Script parameter passing
- True user-based security replaces old inadequate model
FM7 is not ideal. There's still no full-text editing of scripts, and the new multi-table file format does not allow for simple duplication of a table structure. There are some other annoyances, but overall, it's a huge improvement. Existing FileMaker users will appreciate finally getting some of the things they've been asking for for so long. And if you care more about getting your database up and running quickly than you do about esoteric database ideology, FileMaker 7 may be the right choice for your next project.
 NOT a Professional Database Package September 8, 2004
Jorgen Pedersen (England)
8 out of 22 found this review helpful
I agree with the gentleman who suggested that it was not a normalised database, and also with his view of the layout structure inadequacies.
I am a professional developer and system integrator who has developed systems from small applications to global software solutions used across almost any platform.
Filemaker is not a professional tool for the following reasons.
1. The concept of having to have multiple layouts which have to be changed individually is frankly ludicrous.
2. The security of the application is virtually non-existent.
3. The indexing only goes up to 22(or so) characters, so if you have two strings which have the first n characters the same, basically forget it..
4. The printing control is non-existent, particularly if you wish to take control away from the user.
5. The method of opening each related database is frankly ridiculous, and anything complex can very quickly get you to exceed the maximum number of windows open.
6. Almost no logic can be enabled on a print layout, forcing huge numbers of print layouts to be defined, again all which need to be changed manually.
7. Importing and exporting data capability is non-existent.
8. Relationship management and capability is inept and insufficient for serious databases.
9. Encryption is either non-existent or pathetic (sorry cannot remember, but do know that I had to write my own encryption methods as Filemaker could not handle it.)
This is far form a complete list of the real issues I experienced, but is a list of those issues which could have scuppered the entire project if long-winded work-arounds could not have been found and then developed.
In short the application is woefully inadequate, is not professional, and the only thing going for it is that it can create a cross platform solution.
Showing reviews 1-5 of 9
|
|
|
CERTAIN CONTENT THAT APPEARS ON THIS SITE COMES FROM AMAZON SERVICES LLC. THIS CONTENT IS PROVIDED ‘AS IS’ AND IS SUBJECT TO CHANGE OR REMOVAL AT ANY TIME. | |
