As Peter points out it depends on what you are using Filemaker for as to its applicalibity. We use Filemaker to catalogue collections of Molluscs (as it was the only data-base available at the time which we could develop ourselves). We are using it partly as a good label production tool and report-writing rather than a complex collection management system. Although we hope that we have designed the layout to permit (in the long term transfer of the data to a custom built cms system. But as at present our enquiries are at a superfamily level normally with usually less than 4000 records per superfamily we find it is a much quicker tool for getting the data in, and customising for the novice volunteer to use for data-entry in the form we want without waiting for some-else to do it. ie. if you do not need to link lots of files or build up vast lists in one source it is very useful. We do use the look-up facility for correct taxonomic hierachies, as well as automated unique number generation for issuing new accession numbers. We have also used the calculation field in the same way as Peter describes, as well as for any data which we wanted to combined for reports or labels. . We also have the problem of multiple numbers from collections coming into the Museum and found that this system is brilliant for re-numbering and producing new labels for collections instantly, once you have the initial data in. The form building capacity means you can duplicate a copy of for example a site record form from a collecting expedition and get a copy typist to enter the data. Then you edit it, export the completed records to a clone file which allows you to issue unique new numbers in your Musuem format.. I agree with Peter's comments and think FilemakerPro is a great product to start to understand data-bases. It is much easier for some-one with no computer knowledge to set up. "However, like at all flat file databases it has some severe limitations. It is not very efficient in how it uses memory" Remember to compress your files frequently as this helps to manage that problem. "it is very limited in how it establishes relationships between information classes. These limitations are increasingly apparent the larger the files get. Searches, lookups, sorts and other memory intensive actions get slower and slower." Yes, almost inevitable with a flat file - its the price you pay for not having such a comlicated set-up pahse after all! "Filemaker will not handle files over 32 megabytes and once you get over about 25 mbytes it starts crashing far to often. "True But I understand that this will be changing soon - according to Claris! Also, no matter how much Claris implies that a look up is a file relation, it is a primitive one at best." A bit unfair given that it was not designed as a relational database. Claris did demo. their relational version of Filemaker at the last Expo and promise it will be out this year! Filemaker 3.0 will probably answer these problems (at least I hope so) . Another advantage of Filemaker is that it is cross-platform and there is a windows version. If you are anywhere that has mixed PC/mac's this is an important consideration! Few of the lower level data-bases are cross Platform. Hope this helps. >From a relatively reluctant computer convert! Regards Mary Seddon Curator (Terrestrial Mollusca), Nat.Mus.Wales, Cardiff, UK, CF1 3NP E-mail: [log in to unmask] Tel. 44-222-397951x244, Fax 44-222-239009