Fenton, shut the fuck up guy.
er... that's conversational fascism, and worse than anything you've
accused david of, in my HUGEly underappreciated opinion.
Other people suggested Excel, or even file cards. It worked well for them.
(sigh)
again: no one has denied these methods can work. several people have
pointed out the benefits of relational DB over a flat structure,
which you seem to disagree with. fine, but just because you disagree
doesn't mean you're right, which is what you are trying to (rather
forcefully) convince us of by making a "huge... thing" out of
relational DB and essentially claiming they are inherently complex
and therefore not suitable for anyone except DB management types
(with one obvious exception of course). i.e. you haven't really
explained why flat files are better than relational in this case,
except with unsubstantiated claims about relational NOT being the
"best" thing for johannes... who should make that decision for
himself and is probably just avoiding this futile discussion and
shaking his head in amazement... following all of this is more
complex of a thing that actually learning about and building a
relational DB.
Why not the original poster? So I chime in and say I think it is overkill to
have a relational database. Then you go off on a tangent again.
if david (and myself) pointing out what we see as flaws in your
arguments is a tangent, then yeah i guess that is tangental to the
discussion. i've added the appropriate indication in the subject
line to maintain protocol.
As usual. I can play your game too.
well... you don't have to. but if you decide to, let me know what
the prizes and rules are and if it will get me laid and maybe i'll
sign up my team too.
_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale
