I think Filemaker actually will try to complete the field as you type it. So, if you are Typing Amadeus it will complete it before you do.
nope. but value lists come close to this.
A small database of like 1000 pieces can easily be done flat file, and really doesn't warrant a huge relational structure,
a relational structure isn't huge, it's very simple. one composer to several pieces, linked by composer ID.
especially when the person who is setting it up probably does not do that sort of thing in the first place (or else, why would they have been asking).
it's not difficult to learn, especially for someone as computer-savvy as johannes. of course it *can* be done flat file, noone will deny that, but there are risks of incoherencies, and these are in fact greater with multiple users or users unfamiliar with DBs. relational assures consistent entries and when properly built reduces the time spent on data entry, since you enter the composer information once, instead of 40-50 times (the number of scores by that composer).
flat is certainly possible; relational has many advantages over it.
Your points on 14 years of DB yada yada doesn't mean anything in this case.
of course it does, have you ever done any administrative management or project coordination? my comments clearly pointed out that much time and money can be lost by improper use of DBs, and my example pointed out that part of the problems our DB encountered were because it was a flat structure.
.....and it is going past what the original question asker wanted to do. They want to keep track of their music and who has what. This can be done, in the easiest way, on index cards or something, or a flat file database like Bento or Filemaker or something. That is totally what the original poster should aim for.
maybe the original poster should make that decision? and he can do so much better if he is well-informed about what each approach has to offer. there are several people supporting relational databases with explanations of what can be achieved with them and you are simply slamming them with the explanation that a flat structure is another (and apparently better) option that can do the job without explaining what advantage it has over relational.
index cards? are you serious? you mean those paper cards!?
On the flip side, a relational database is very easily messed up. You delete the foreign key to the composers table that was linking song titles to their composers. Not easy at all to fix. And a lot of people who have no database experience can very easily do this.
and an index card can get lost or filled and have to be replaced. and a file can get corrupted. and someone can duplicate the file and enter information in the non-master file. and your computer can be stolen. you can't base decisions on unknowns and expect any real progress to happen. the best is to plan it out well at the start and plan for the future.
why the reactionary response to relational DB structures? _______________________________________________ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
