I took a look at your db model, and it was definitely far too much...
With the diagram pic I have attached, you have the db structure you need to accomplish the assignment.
I'm looking into to some other parts of the db, mainly the forms, im not sure why there are some in the access db itself (perhaps the guy was just testing it)
Well, first off- I have a revised model, don't worry too much on the database, ill upload it once im done revising it.
Here's a few questions though:
true or false...
1) An appointment can be made because of one or more ailments?
2) An appointment can have one or more results... ?
I assume true to both.
There is no need for a patient history table, because really all you are going to do is check the appointment table for anytime that patient made an appointment. With that data, you will be able to surmise what ailments there were, and/or what results (refered, given a prescription, etc).
Attached is a pic of what I believe is the final model of the database.
ONE MORE QUESTION: Does your assignment requires that the database has forms, or just the VB6 app, or do both need to have forms (for instance, if you open up the database and in the forms, you will see Patient... does that need to be there?)
Last edited by nemaroller; Dec 8th, 2004 at 11:45 PM.
We have appended our relationships to the specifications in your attatchment. We are attatching the new vb, can you see if this is correct as you obviously have much more of an insight than us.
Your project requires you be able to append one or more ailments, and one or more results to any one appointment.
Like I said, I have the database side finished except for one question...
DOes the database need to have forms inside of it? Yours did... I think maybe only so the person who created it could test his relationships... I didn't see anything in the project requirement that stated so.
If the database doesn't need its own internal forms, then I can upload the db to
you right now, and start helping you with the vb side.
I've been through this once before long ago myself, so I know where you're coming from.