Need help with my project

[samia]

Hello Everybody,

I thank you for this great resource. It's helped me a great deal on my project.

Now, my problem is: I want to have a fully fledged DB system with reports and all. I know DB development is a process and that I'll keep adding more tables. However, for now I need to get this DB working for data entry. But judging from the level of computer literacy of my clients I would like to design a form that will make data entry easy i.e. after the data entrant enters the patient info, they are supposed to enter the risk behaviours if any then they go on to enter the complaints. (I'll eventually have tblTreatmnt, tblDoctor).

Any suggestions. I highly appreciate.

Samia

 

[ColinEssex]

I would suggest using the form wizard to create the form for patient demographic data input, then use buttons to link to the risk and complaint form.

Having looked at your patient table, I would strongly suggest you use an AutoNumber for the Patient ID and use your present one as a normal field. Its easier to use the autonumber for links rather than a 'human' input ID (they'll get it wrong for sure)

What actually is the database for? is it visits to a GP or something?

Col

 

[Kraj]

I agree with Colin, and also strongly suggest you complete your tables before going further. It can be a large pain to change tables once you've begun to create forms, queries and reports. And if you add tables later on that have any relationship to the existing tables, you may mess up your normalization.

 

[samia]

I would strongly suggest you use an AutoNumber for the Patient ID and use your present one as a normal field.

So do I change in all the tables where I have Patient ID to AutoNumber?

What actually is the database for? is it visits to a GP or something?

Yes, it is visits to a clinic.

 

[Kraj]

Well, it depends. If each patient has an ID number that appears on their paperwork (or has any other use/meaning to the end-users) then what you want to do is leave the patientID field as a field that users can see, input and change. Then add a new field to the table, set the data type to autonumber and use that as the table's key. Any references to patientID in your existing tables should use this new field and not the current one.

If, on the other hand, patientID is intended to be nothing more than the table key and the user never has to see it, then simply change the patientID in the patient table to autonumber. You do NOT want to change patientID in any other tables to autonumber; they should stay as general number. This is because an autonumber field will always generate a random number instead of using a matching number in each table. Let me know if that doesn't make sense and I'll try to explain it better.

 

[samia]

Thansk so much Kraj,

I've now created a new PK ClientID, should I conitnue to create it in all the other tables for linking purposes. My PatientId has meaning to users.

P'se I want a fully fledge DB so that when I get to doing reports I have little trouble.

Thaks in advance,


Samia