ACCESS FEED: RE: [MS_AccessPros] Opions plz, continued from discussion with John V. re: LOTS of Tables

Sabtu, 27 Agustus 2011

RE: [MS_AccessPros] Opions plz, continued from discussion with John V. re: LOTS of Tables

hi Duane,

thanks Duane, nice to see your message :) your survey app looks great! I grabbed it to look at sometime in the future ...

Between teaching, being mom and caretaker, yardwork, ..., I've been learning and writing apps for the Windows Phone. Made a new YouTube channel for my non-Access tutorials:

http://www.Youtube.com/LearnByCrystal

The temporary video posted will get deleted -- am testing resolution. Watch it in 720p full screen! who needs sound? ;) I will add audio, and intro, and a closing ;)

> Remember, you are the person who asked for the diagram.

yes I did ... and I can't find where he posted it ;) The database does not have an organized diagram

> need to be Crystalized ;-)

I can see your smile, thanks :)

Warm Regards,
Crystal

*
(: have an awesome day :)
*

--- On Sat, 8/27/11, Duane Hookom wrote:

>
> Hi Crystal,
> It's good to see your postings again. It's really great
> after reviewing Terence's relationships. The table
> structures need to be Crystalized ;-)
>
> Remember, you are the person who asked for the diagram.
>
> Duane Hookom
> MS Access MVP
>
>
>
From: strive4peace
>
> Hi Terence,
>
> make a PowerPoint presentation (or Word doc) with screen
> shots of your relationship diagram laid out according to the
> guidelines in the Relationships chapter of Access Basics and
> post them. I would like to see your structure.
>
> Access Basics by Crystal (Bill Mosca's site)
> http://thatlldoit.com
>
> Warm Regards,
> Crystal
>
> *
> (: have an awesome day :)
> *
>
> --- On Sat, 8/27/11, Terence wrote:
>
> > I have been working on a DB which
> > started out small and grew LOL. It is a
> medical/statistical
> > DB, and the General format was an Information Table
> > (Patients name, address, etc), An Office_Visit Table,
> > consisting of measurements taken during that visit.
> Very
> > Straight forward.
> >
> > Then it turned out that the measurements taken during
> each
> > office visit were derived from tests which required
> either
> > specific calculations or questioners. So what I did
> was to
> > create a popup form for each test or questioners.
> These
> > detailed elements of information were then stored in
> a
> > separate table linked to the office visit.
> >
> > Well I now have over 40 potential tables per office
> visit
> > and counting.
> >
> > In discussions with John V. (Which you can follow on
> our
> > forum). John suggested that I consider making each
> test a
> > ROW of the Visit table, thus reducing the number of
> table
> > significantly.
> >
> > Now be aware, these probably only 50 % of these test
> are
> > actually performed during a visit.
> >
> > John seemed to be uncomfortable with the large number
> of
> > tables, and seemed especially concerned about DB
> size.
> >
> > I am looking for comments suggestions, and any case
> > experience from other member with a similar situation.
> I
> > wrestle with LOTS of tables, BIG DEAL, "thats what a
> DB is
> > for". Or should I take a more conservative approach
> and make
> > the various test data as rows to the Visit ?
> >
> > Pit Falls ? Pros Cons ?
> > terence
> > TY in advance.
> >
>
>
>
>