Re: My form won't open since I created a macro

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I think I understand. The patient would have a one-to-one relationship with
his name, his medical record number, his birthdate, his admission date and
his discharge date. Month 1 would have a one-to-one relationship with the
different due dates for that month only. Month 2 would have a one-to-one
relationship with the due dates entered for that second month only, etc. So
there would have to be a table for the patient, another table for Month 1,
another table for Month 2, etc.

It seems then that an Excel spreadsheet might be more appropriate. I was
hoping to do queries and create reports from the data which is why I thought
of Access. Plus I never learned Excel. Perhaps it is time that I did.

Thank you, Steve for your time and consideration of my proposed project. I
appreciate your help.

"Steve Schapel" <schapel@xxxxxxxxxxx> wrote in message
news:OdjrhzwFJHA.3392@xxxxxxxxxxxxxxxxxxxxxxx
Linda,

Well, it's not exactly that it *can't* be done. Just that it
*shouldn't*. It's the kind of thing you would see in a spreadsheet and
stuff like that. But in a database such a design is called
un-normalised. In a databse, we would recognise that there is a
one-to-many relationship between the entity of the person, and the
entity of whatever is represented by the M1-M12 fields, and as such
needs a separate related table. As for the presentation of this data on
a form, the standard approach would be a main form for the data on the
"one" side (i.e. person specific) and a continuous view subform based on
the "many" side table(s).

Hope you understand.

--
Steve Schapel, Microsoft Access MVP

Morgaine wrote:
Hi Steve:

I was going to have 12 fields per record in the table and 12
cooresponding
controls on my form. The idea was that the "Initial" entry would
populate
the data into the twelve field in the table and show on the form. It is
for
a dialysis unit where there are monthly, semi-annual, and annual reports
due, all starting from each individual's admission date. So Month 1 for
each person may be different. If I am understanding you correctly, this
can't be done with a data base form. I have attached a couple of
graphics
(if the newsgroup will allow it) in case I am not explaining it clearly.



.

Relevant Pages

  • by Eric Skjei. The mythical medical record.
    ... relational database and the longitudinal patient record. ... The mythical medical record ... The net result, of course, is that frustrated clinicians ... open computing environment in health care. ...
    (sci.med.informatics)
  • Re: Why is this query not updatable?
    ... the DMax function in qryLastAttending and qryLastResident. ... For each admission, there will be one or more attendings taking care ... patient (patients can be transferred sequentially from one attending ...
    (microsoft.public.access.queries)
  • Re: Why is this query not updatable?
    ... For each admission, there will be one or more attendings taking care of ... patient (patients can be transferred sequentially from one attending to ... I created a query (qryLastAttending) based on tblLINK_AdmissionAttending ...
    (microsoft.public.access.queries)
  • Re: Why is this query not updatable?
    ... the DMax function in qryLastAttending and qryLastResident. ... For each admission, there will be one or more attendings taking care of ... patient (patients can be transferred sequentially from one attending to ...
    (microsoft.public.access.queries)
  • Relation between quality control and medical dispute of the medical record
    ... Medical record whether clinical medical personnel transform into ... In the medical dispute, doctors and patients' ... patient and presented the bad consequence directly. ... The quality of the quality of the medical record is running ...
    (soc.retirement)