I'd like to add one more thought to the "plan well before
starting" idea --
Once you have it planned out, enter only 5 or 10 works, with
all the data as you have it planned out, then run some
typical queries on it to see if it will give you the
information you want.
There's nothing worse than thinking you've got it all
planned perfectly, entering 100 or more works, only to find
out that you have to go back and re-enter a lot of data or
break what is currently one field into two fields, etc.
And as you plan, think about what might be needed in 10
years or 20 years, not just what might be needed in 6 months.
David H. Bailey
George Brooke wrote:
I'd like to add my vote for FileMaker Pro. I'm a choral director and find it
to be very flexible, easy to use and able to do just about anything I can
dream up.
One of the keys is what several have already mentioned about planning what
info you need and how you're going to be using and entering it before you
start actually setting up your database in FileMaker. My suggestion here is
use more fields rather than fewer. Once you have the info entered you can
search on any field.
George Brooke
Director of Music
House of Hope Lutheran Church
New Hope, MN
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Johannes Gebauer
Sent: Tuesday, August 19, 2008 12:38 AM
To: Finale
Subject: [Finale] TAN: building a database for a music library
My orchestra needs to create a database for its small, but growing music
library. Can someone give me some hints on how to do this, preferable on
a Mac? I want something which is easy to maintain and where I can see
how many string parts we have, perhaps also who borrows which part, etc.
Johannes
--
David H. Bailey
[EMAIL PROTECTED]
_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale
