By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
431,827 Members | 2,267 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 431,827 IT Pros & Developers. It's quick & easy.

add fields to a form from a table with criteria

P: 2
Hi there
I'm trying to add several fields to a form from a table that has criteria towards obtaining a specific risk index. In the lookup table, there is: (the first column is the heading and the next column is an example)

Disease_type: Acute myelogenous leukemia (AML)
Characteristics: favourable cytogenetics
Remission: complete remission (CR)
Stage: early

If these are the criteria/disease status, then the corresponding risks are also listed in the table as succeeding columns:

Disease Risk: Low
2yr_OverallSurvival: 66%
95% Confidence Interval: 63-68

- To create a combo box for each criteria from the table but with only one type of the disease/characteristic/remission/stage appearing in the dropdown list.

- To create disease risk boxes based on the disease criteria provided in the combo box.

- To store these data into each patient's record.

thank you very much for your help!

Apr 28 '16 #1
Share this Question
Share on Google+
4 Replies

Expert 100+
P: 1,430
A few ideas to start you off:-
3 tables:- One for Patients with PatientID as Key
One for Diseases with DiseaseID as the key and the 7 fields you have mentioned.
One JoinPatientDisease with a joint key of PatientID and DiseaseID

Main form for Patient
Subform for that Patient's disease
Combo box to select the disease from all the diseases in your database.

As I said, that's your starting position

Apr 29 '16 #2

P: 2
Hi PhilOfWalton!
Thanks for your response!
We have the first two tables you mentioned: Patients table (with demographics and other disease details, treatments for each patient) and the lookup table with those 7 fields.

I will create a subform for the patient's disease status and the risk index.

thanks for letting me know of the next steps.

Apr 29 '16 #3

Expert Mod 5K+
P: 5,397
First, welcome to!
You really should read thru Database Normalization and Table Structures either as a refresher or as a new database developer.

Properly designed databases are your friend, whereas, those lacking the proper normalization can become things of nightmares!

You may also find: Cascading Combo/List Boxes worth a read along with other entries in our Insights Articles (see the VBA Insights link at the bottom of this page :) )

As you progress thru your project, the most common mistake made is to treat the database tables like one would a spreadsheet by creating multiple columns for information when a new table with a foreign key to the parent table is most often the better way to accomplish the task.

PhilOfWalton has certainly given you one option and there are several other variations on the theme that would accomplish the same task.

One thing that will help us to help you is a better understanding of your skills with Access and relational databases along with which version of Office/Access and operating system you are working with.

Finally, we can answer specific questions and often give a good starting point (as Phil has done); however, building a project from scratch as often beyond what we can do in a forum setting - never fear, we'll do our best!
Apr 29 '16 #4

Expert 100+
P: 1,430

I am a more than a little concerned that you say "Patients table (with demographics and other disease details, treatments for each patient)"

As zmbd advises, look up on normalisation.
To explain further, Patients are just people who may or may not have a disease (though I suppose you could argue that they wouldn't be patients if they weren't ill). So your patients file should only hold "fixed" information such as names, sex, height, weight etc. Even things like addresses are not really part of a patient - they move houses and I tend to keep address in a separate table.
Their diseases come and go, so are not "fixed" information.

Equally diseases exist in their own right so are in a separate table.

Your task is to link the person to the disease when they become ill and that is what the Join table I mentioned is for. It allows a patient to be linked to as many diseases as is necessary and from the other point of view, link a disease to as many people as necessary. The Join table can also hold other information such as date diagnosed, doctor's name and hopefully cured. If they have been cured, you still have the record of their problem, but it is no longer relevant.

So you can easily get information as to which diseases this patient is afflicted with, and the other way round is "who has got 'flu?"

Treatments should be in another table, but that can be dealt with later.

Apr 29 '16 #5

Post your reply

Sign in to post your reply or Sign up for a free account.