Ideas

[ICTkirsten]

Hello,

Im currently trying to think of a way i can input details about a dental appointment .
I was thinking to have a form containing the fields : TeethID, CustomerID, ,front teeth, back teeth...

so the front teeth and back teeth are going to be figures that i input ..

I need these figures to save and be somehow linked to the customerID because the teeth are for that customer.. and so i can also see that customers teeth history. ( if this makes any sense)

Im not to sure about the purpose of the teethID and why it needs to be included but i need something to be a primary key right?


Im really sorry about this messy explanation but im really stuck and any help would be great

Thank you

 

[Frothingslosh]

If it helps any, dentists simply number teeth 1-32. Each number represents a very specific tooth, and the numbering is standardized across the profession.

If you make a 'teeth' table, it would basically have tooth number, tooth description, and perhaps tooth location (although as I said, the numbering is always the same - tooth 1 is the left upper wisdom tooth, tooth 17 is the left lower wisdom tooth, and tooth 32 is the right lower wisdom tooth). The primary key would be the tooth number.

For your appointments, you would really just need an appointment ID (PK for linking), patient ID (linking to a patient table with certain minimal requirements such as name and phone), appointment date, appointment date and time (1 or 2 fields as required), and appointment reason (I'd say memo).

Leave the tooth business for tracking what was actually done.

Have you looked to see if there were already any templates made for something like this? I don't have my template links available atm, but a quick Google search pulls up a ton of them.

 

[namliam]

Well start at the base of the base, what is the purpose of your information?
What is the goal you are trying to achieve?

Start with that and then start with the normalization process of making tables and worrying about Primary Keys and such.