Automatic Update of Fields on Form

  • Thread starter Thread starter Dwain
  • Start date Start date
D

Dwain

I wonder if there is a way for a form containing
Eg. "List1" thru "List10" to be updated Sequentially.

You enter data for "List1" today.
Tomorrow as you enter data for "List2", "List1"
automatically updates and carries forward the data
from "List1" yesterday & so on.

What I need is for 10 lists to update automatically so
that as I add more encounters for this event, the prior
List values are carried over to the new date. If there is
nothing new to add to "List#" then it continues with
yesterdays values to the List# that has data
eg. "List1" "List2" "List3" etc.

If this is unclear please let me know...
 
I wonder if there is a way for a form containing
Eg. "List1" thru "List10" to be updated Sequentially.

You enter data for "List1" today.
Tomorrow as you enter data for "List2", "List1"
automatically updates and carries forward the data
from "List1" yesterday & so on.

What I need is for 10 lists to update automatically so
that as I add more encounters for this event, the prior
List values are carried over to the new date. If there is
nothing new to add to "List#" then it continues with
yesterdays values to the List# that has data
eg. "List1" "List2" "List3" etc.

If this is unclear please let me know...
Click to expand...

STOP.

You're approaching this problem from the wrong end. The foundation of
an Access application is a set of properly normalized tables; a Form
is *just a tool to look at and edit the data in those tables*.

If you're storing the same kind of data in ten tables (named List1,
List2 and so on), and trying to move data from one table to another,
stop; step back; and reconsider your table design. It sounds like you
have a one-to-many relationship between Events and Encounters; a
better design might be to have a table of Events related one to many
to a table of Encounters, with a date field in the encounters table.
This could be displayed on a Form with a Subform, showing all the
encounters for an event in chronological order.
 
What I want to do is the following:
I have a list of Diagnoses >15000 items. A Customer can have more than
1 Diagnosis per visit. Therefore I don't need 10 Diagnosis Lists, just 1
Diagnosis List and 10 Fields in an Events table linked to this 1 Diagnosis
List.
When a Customer pays a Visit I want to be able to add a new Diagnosis which
I pick from the Diagnosis List, and have it include the preceeding
Diagnosis(es) already selected from prior visits.
Example: Date=01/18/2004; Dx1=Cough; Dx2-10=Blank
Date=01/24/2004; Dx1=Cough; Dx2=Fever; Dx3-10=Blank
Date=01/28/2004; Dx1=Cough; Dx2=Fever; Dx3=Chills;Dx4-1-=Blank
Thanks...
 
I have a list of Diagnoses >15000 items. A Customer can have more than
1 Diagnosis per visit. Therefore I don't need 10 Diagnosis Lists, just 1
Diagnosis List and 10 Fields in an Events table linked to this 1 Diagnosis
List.
When a Customer pays a Visit I want to be able to add a new Diagnosis which
I pick from the Diagnosis List, and have it include the preceeding
Diagnosis(es) already selected from prior visits.
Example: Date=01/18/2004; Dx1=Cough; Dx2-10=Blank
Date=01/24/2004; Dx1=Cough; Dx2=Fever; Dx3-10=Blank
Date=01/28/2004; Dx1=Cough; Dx2=Fever; Dx3=Chills;Dx4-1-=Blank
Click to expand...

This is not a properly normalized design. "Fields are expensive,
records are cheap" - if you have a many to many relationship between
Visits and Diagnoses, a proper table structure is to model it *as a
many to many relationship*, by adding a VisitDiagnosis table with two
fields: VisitID and DiagnosisCode. You might want additional fields,
such as a severity field, a ranking (primary diagnosis 1, secondary
2...), or a comments field... but if a patient has eleven complaints
at a visit, you'ld add eleven rows to this table using a Subform.

Storing this relationship in ten fields will be inefficient and make
it MUCH more difficult to (say) find all the patients suffering from a
particular symptom.
 
Back
Top