The holiday hangout will go online tomorrow! If there's anything in the regular subforums that you're going to want to access over the holidays, copy it now while it's still accessible.
Our new Indie Games subforum is now open for business in G&T. Go and check it out, you might land a code for a free game. If you're developing an indie game and want to post about it, follow these directions. If you don't, he'll break your legs! Hahaha! Seriously though.
Our rules have been updated and given their own forum. Go and look at them! They are nice, and there may be new ones that you didn't know about! Hooray for rules! Hooray for The System! Hooray for Conforming!
Database Structure & Business Practice w/Joint Accounts
I'm having a problem wrapping my head around this and was wondering if I could get some help.
I'm building a database to handle kids taking classes. As I have things built each kid basically acts as an account. They live in their own table and are linked to classes, payments and parents (in a contact table) all linked through primary keys.
One kids takes classes and pays off those classes... easy enough right.
Unfortunately kids have these damn things called siblings, so as things go one parents pay for say 2 accounts with 1 check and we enter that 1 check into the system 2x. I see that as kind of bad because we now have 2 records for 1 payment. Also as it currently stands, only 1 kid can be linked to infinite parents because I can only really have 1 key linking the individual records in 2 tables.
How can I make 2 accounts act like 1? Do I put a kind of joint table between some table relationships? Ideas?
(i'm building this in filemaker, but I figure the db structure philosophy should universally be the same... right?)