[EMAIL PROTECTED] wrote:
I'm not sure whether you mean you need help setting up a catalogue system or a loan system. I am presuming the former. I use a normal everyday database program to organise our library - (we used to use the database program in Microsoft Works then changed to Paradox which is much more powerful) Each category has a separate table (file) :- orchestra; string orchestra; wind band; brass band; flute group; clarinet group; wind ensemble. The pieces are catalogued under the name of the composer and I print off a catologue listing the pieces in order of composer and in order of title. Even if the catalogue is lost or stolen, so long as you know the name of the composer (and you should) most pieces can be found within seconds. Of course there's still the computer database which can be searched until a new copy is printed. (One department was setup by someone else and pieces are simply added to the end as they are bought. This works perfectly until the printed catologue disappears, then you have to search through over 800 folders until you find the one you want - I'm hoping to sort that one out soon!) The same programme also prints labels for the boxes/folders.
Great advice, Lawrence -- I use a similar system for my town band's library, but I have all titles in a single database (it's easy to keep straight). I use a key field so that I can sort the database according to type, using the first letters of the following types of music: Concert, March, Xmas (this incorporates all our holiday music, even if it is for Chanukah or Kwanzaa or New Year's or simply winter-related).
My next great organizational step will be adding a Solo key so that I can rapidly find all our works for band with clarinet solo, for example.
Now if the original question really does concern how to handle a lending system, I don't have an answer that doesn't require a lot of personnel time.
But it could also be done using Paradox or any other relational database, since they are designed for just such things. The problem, however is setting the system up and then maintaining it and also enforcing that procedures are all followed precisely. This sort of database system would of necessity require the assistance of someone experience in relational database design and maintenance.
-- David H. Bailey [EMAIL PROTECTED] _______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
