A
Allie
I'm working on a database for a huge amount of information that realistically
is related ONLY by a person's ID number, unless I'm just not thinking of it
correctly. Basically we collect general demographic information and
information about the person entering the info (I lumped this all in as a
drop-down in the box because it's only one variable and we don't really need
another table to explain who's who). My "main table" is [Main], which
contains information on the following: General Case Information, Last
Specialist Visit, Last 12 month medical overview, and Life Events. I didn't
break these down into separate tables because each person will only have one
entry for each of them and I wanted them to be on the same form. Then I have
other tables: [Last Visit] which contains all visits to any provider on a
given day, [LVMDx] which contains last visit diagnoses from any of the visits
in the [Last Visit] table, [LSVDx] which is only diagnoses from the last
specialist visit, [SA] which contains information on substance use at various
points in time when it was evaluated, [SI] which contains other assessed
medical information at specific (different) timepoints, and [Events] which
contains the ID and year/time of event.
Is this a viable way to break down the information? The people I work with
prefer more information in one table to a lot of information in other places,
so for the most part all my relationships are one-to-many and based on ID.
Earlier on I attempted to integrate the [Last Visit] with the [Main] table
and ended up in a situation where you could add a new subject but evidently
not enough of a new subject to "make it stick" in form view - so it would be
a poor sad little nothing in the table, and I'm hoping to find a way to avoid
that. I don't know if it was related to my setup, or ???
Also, was having errors with multiple people trying to access the DB at
once. I'm not sure if that was a remote server problem or if it was a bad
database problem, but if anyone has any light to shed I would appreciate it.
is related ONLY by a person's ID number, unless I'm just not thinking of it
correctly. Basically we collect general demographic information and
information about the person entering the info (I lumped this all in as a
drop-down in the box because it's only one variable and we don't really need
another table to explain who's who). My "main table" is [Main], which
contains information on the following: General Case Information, Last
Specialist Visit, Last 12 month medical overview, and Life Events. I didn't
break these down into separate tables because each person will only have one
entry for each of them and I wanted them to be on the same form. Then I have
other tables: [Last Visit] which contains all visits to any provider on a
given day, [LVMDx] which contains last visit diagnoses from any of the visits
in the [Last Visit] table, [LSVDx] which is only diagnoses from the last
specialist visit, [SA] which contains information on substance use at various
points in time when it was evaluated, [SI] which contains other assessed
medical information at specific (different) timepoints, and [Events] which
contains the ID and year/time of event.
Is this a viable way to break down the information? The people I work with
prefer more information in one table to a lot of information in other places,
so for the most part all my relationships are one-to-many and based on ID.
Earlier on I attempted to integrate the [Last Visit] with the [Main] table
and ended up in a situation where you could add a new subject but evidently
not enough of a new subject to "make it stick" in form view - so it would be
a poor sad little nothing in the table, and I'm hoping to find a way to avoid
that. I don't know if it was related to my setup, or ???
Also, was having errors with multiple people trying to access the DB at
once. I'm not sure if that was a remote server problem or if it was a bad
database problem, but if anyone has any light to shed I would appreciate it.