At 18:14 -0400 08/02/1999, Chris Nandor wrote: >Depends on the needs. I actually have databases with many fields (6-12) >that number more than 15,000 records (25K or so?), and DBM is the best >approach in this case, as it takes up the fewest resources and gives me the >fastest access. The database is also completely static, so I don't need to >do any updates, and I don't need to run any queries other than a simple >fetch to a key. So as I said, depends on the needs. True, but depending on the nature of the data, another consideration is whether using a single flat file is appropriate in itself (meaning that it's fairly likely that something with 15 fields that I assume is being used to catalog book inventory probably is in dire need of a relational schema). There is also the question of data validation for which I wouldn't think DBM would offer much support. However, I would agree that there's not much point in complifying things if the data is pretty static, you don't do multifield queries (in fact I don't even think you can with DBM, can you?), and multiple users aren't a big issue. Richard Gordon -------------------- Gordon Consulting & Design Database Design/Scripting Languages mailto:richard@richardgordon.net http://www.richardgordon.net 770.971.6887 (voice) 770.216.1829 (fax) ==== Want to unsubscribe from this list? ==== Send mail with body "unsubscribe" to macperl-anyperl-request@macperl.org