I believe what you are describing could be displayed using a "main form" to
hold the patient info and a subform to display the visit info.
Regards
Jeff Boyce
Microsoft Access MVP
--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.
Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.
You can thank the FTC of the USA for making this disclaimer
possible/necessary.
"John" <Jo...@discussions.microsoft.com> wrote in message
news:F6EF2E6C-10F8-474C...@microsoft.com...
STOP.
You do NOT need multiple forms for multiple records. Your visits are not
stored in Forms! Your patients are not stored in Forms! Information about both
are stored in Tables; and the Forms let you manage data stored in those
tables. A form is just a window, a tool to let you look at and edit data
stored in a table.
If you have a one (patient) to many (visits) relationship, you need two
tables: a table of Patients (with a PatientID as a primary key) and a table of
Visits (with fields for the PatientID as a link to Patients, VisitDate, reason
for the visit, weight at the time of the visit, whatever other info you need).
Take a look at some of these resources. Crystal's tutorial and video might be
the best start:
Jeff Conrad's resources page:
http://www.accessmvp.com/JConrad/accessjunkie/resources.html
The Access Web resources page:
http://www.mvps.org/access/resources/index.html
Roger Carlson's tutorials, samples and tips:
http://www.rogersaccesslibrary.com/
A free tutorial written by Crystal:
http://allenbrowne.com/casu-22.html
A video how-to series by Crystal:
http://www.YouTube.com/user/LearnAccessByCrystal
MVP Allen Browne's tutorials:
http://allenbrowne.com/links.html#Tutorials
--
John W. Vinson [MVP]
I mis-spoke ... you need a main form to DISPLAY the patient data and a
subform to DISPLAY the visit data.
Regards
Jeff Boyce
Microsoft Access MVP
--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.
Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.
You can thank the FTC of the USA for making this disclaimer
possible/necessary.
"John" <Jo...@discussions.microsoft.com> wrote in message
news:F6EF2E6C-10F8-474C...@microsoft.com...
I REALLY wanted to answer this one because it's within my set of
skills but John and Jeff just HAD to steal my thunder.
Could you smartie pants MVP-types please leave these more fundamental
posts to users like myself who might find some bit of joy in being at
least a little useful? I mean, don't you have something more
challenging to help with?
Really.
:)
>I REALLY wanted to answer this one because it's within my set of
>skills but John and Jeff just HAD to steal my thunder.
>
>Could you smartie pants MVP-types please leave these more fundamental
>posts to users like myself who might find some bit of joy in being at
>least a little useful? I mean, don't you have something more
>challenging to help with?
<blush>
Nothing stopping you from posting your own (at this point probably very
helpful!) point of view!
I thought you and Jeff covered it pretty nicely - as always!
On Jan 6, 12:11 am, John W. Vinson
Jeff B.
"johnlute" <jl...@marzetti.com> wrote in message
news:2280aeff-4377-4fb8...@k19g2000yqc.googlegroups.com...