Printable View
were in a group project in vb 6 here in college and we are very very stuck in our hospital program, that we are making. we cant seem to get simple things to work
like:
adding searching and deleting records from a database.
and looking up medical history.
if any of you would look at it and point us in the right direction that would be super....its 2am here and it has to be in for 12pm (a few hours away)
I can put it on a server?
And the database type is what? Jet, MySQL, Oracle ???
MS access
you should zip you code then attach it to your post so someone can look at it :thumb:
will do, its coming now....thanks so much :thumb:
Here it is
the brief is here
any help at all would be so greatly appreciated, decides basically if we stay in uni this year!!!!
http://www.infj.ulst.ac.uk/~cnugent/...ssignment2.pdf
Guys - you can't be serious. What have you been doing all year?
snowed under with other assignments and got screwed over so many times by other people.
down to time management and we have a lot to learn :S
Given your timescales - why not switch to an access project instead.
we have no choice, we have to do
ERD diagram (done)
Access (done)
VB (not done)
ASP link (working on)
this forum ahs been the last chance for us in getting help, there is no one anywhere else on.
can anytone please help with anything?
The VB part of the assignment is worth 50 points, I'd work on that first.
Easiest thing to do is to use a datagrid for listing, entering and deleting patients. Of course, its been so long since I've used vb6, i couldn't tell you where to even begin anymore.
scroll down to the 'Doing Databases' section
http://www.theopensourcery.com/vb08tut.htm
Well your screens look OK, but you are relying on bound controls everywhere. It is not easy to follow any program flow with that I am afraid.
Also, I was amazed that there was not a single module in your project - just forms.
A hint or two and a good solid answer on a sticky point - yep, no problem - this is the place. But a project write is asking a lot. Sorry guys, Its 2.17AM my end and there is no way I could start it let alone fit it in. I am almost asleep at the keyboard now.
I wish you luck - you are going to need it. :(
thanks for the reply, the VB is what we are really stuck at.
would you be able to take a look at what we have uploaded and tell us what is wrong with our code to add and search
?
we will pay pal money!
Whats' your password
and where is it kicking in? From the database or the code itself?
doctor
what do you mean by your last post?
No problem - scratch my last post - i am in
you are our hero
OK - i can see your problem - give me 10 minutes
OK - do this with me - remove all of the index references in the textboxes on both the Add form and the Delete form
Then it should work.
Just trying it my end
just enter a space or delete the number that is there
doing it now
removed all index references from both
OK - that free's up the forms so they should do the job. I have just had a look at your database and the relationships are huge.
When you try to add a record now, one of the relationships is stopping you from doing that. As you built the databse I am afraid that one is yours to figure. But your add and delete forms should now work. I will re-post so you can see what I did.
Don't use my project as i had to point the data objects to a different directory to get at the database.
EDIT - Typos and attachment
runtime error 3265
when adding
You get the same problem when trying to delete. To many interrelated tables. You may need to release some of the relationships in order to get add and delete to work. But then things may not work as you intended.
That's all I can do for you guys.
Good luck and goodnight.
thanks for the help, not much further forward but well let you know when were on the dole
:bigyello: Perhaps you need to think about a change in career direction.
On the face of it it may look like you are close to a solution but the two parts don't hang together. your best bet is to find the guy that did the database and get him to change the table structure around to match your code.
The database being the more complex of the two codes.
oh no, i just enjoy making sites :(
what should we get rid of? ?!?
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)
what now?
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?)
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.
>(post just to notify you) see post #36
we are really stuck if we can keep it very basic that would be best, i dont think we have time to add more stuff :S
Well...
here's your command decision then.
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.
the database does need forms we think. more visual way of displaying. if you think of something better(or easier) then well listen.
crowded round here awaiting your answer!
cheers
Well, I don't think it does... (im very positive about) simply because the project requirement pdf you posted does not state it does, only requires vb6 forms from your vb6 app.
Anyway, here's the database...
thanks for your help, but what do we do with this?
its very different and confusing from ours is it not?
:s
The doctor logs in from the login screen....
MainForm:
You need to display a list of appointments for the doctor that logged in, in the page_load, retrieve any listing in the appointments table that has the GPID. These will be buttons or whatever that load up the AppointMentForm (described later).
You also need to be able to have the doctor make an appointment with a patient. So on the main form, you will need a button that opens up the Appointment form for new data entry.
Also, a new patient button that opens a new patient form, that will save new patient names, address into the db.
And lastly, a button that says 'search patients', which will take in a last name or first name or both, and open a form a PatientHistoryForm.
PatientHistoryForm:
Looks up all appointments in the database, finds any related Results and Ailments and lists them on the form perhaps with the date of the appointment.
12/02/2002 Fever Given Tylenol
Appointment Form:
Gives the details of the appointment
12/02/2002 John Smith Dr. Franks
[Add Ailment] [Add Result]
Really, you do have quite a bit of work ahead of you...
I'd help you out, but its late her, and since I moved to .Net over 2 years ago, I don't even have a VB6 IDE to help with that part.
The database is simpler than your model and is efficient, so you should be able to wonders if you understand what you are doing.
thanks for your help man, greatly appreciated :afrog:
well survive :duck:
Nice one namaroller. I was amazed to see so much interdependancy in the database. A question for you If I may. In what way are relationships within the database usefull as far as the application is concerned. Are they seen as hard coded inner joins at the SQL level?
Relationships in the database are firstly important for the integrity of the database itself - you have to visualize and enforce these even if you never connected an application to it. I enforced a few cascading changes and deletes too(looking back this morning, there should have been a cascading update rule between patients and the appt table, and the doctor and appointment table, but oh well :) )
As far as the application though - if you send a sql statement to delete an appointment, then all details of that appointment should be removed - this includes any ailments the patient described over the phone before the appointment because these were not verified in person.
End result, once you delete the appointment, any related records will also get deleted by the database automatically, so the application does not have to look for related records manually. (So a sql statement from an application 'Delete from Appointment where patientno=12 and apptdate=12/12/2004' will remove the appointment AND any entries from the ailments table, because of its relationship. You would not have to issue another command 'Delete From Ailments Where fkAppointmentNo = pkAppointmentNo Inner Join On Appointment....
Or, deleting a patient because they became deceased, you may want to remove any of their patient history-so all appointments and his related ailments will be removed)
Since you brought it up though, they would require an inner join to retrieve the ailments to compose a patient history (since they would have to first find all appointments for a particular patient, and inner join those on any ailments with a matching appointment id)
I wonder how far they got...
I was wondering that also, but given that they only joined up to sort out this project at such a late stage they won't be VB die hards so chances are they won't be back.
prolly turned something in, even if it wasn't right. teachers don't try to debug things, and like to give partial credit to things that they recognize as being correct. maybe they were able to slide through. i don't think that they finished it, though.