Need interface design reccomendations

  • Thread starter Luke Dalessandro
  • Start date
L

Luke Dalessandro

Access 2000

What's the normal way for doing this?

I have tables:

A B C
AID-\ BID-\ CID
\-AID \-BID

My goal is for users to browse to a record in "A" and then be able to
see a list of "B"s associated with "A" and each "C" associated with each
"B".

This is easy enough on a report, but I need to show it to them on a
form. I don't want to use datasheets or to join "B" and "C" into one
continuous subform because that doesn't really fit what I'm modeling,
and will confuse the users that I have.

The only thing I can think of is to have a main form with two continuous
subforms. The main form is bound to table A. The first subform is bound
to table B and is linked by AID. The second subform is bound to table C,
but is not linked.

There is a button on subform B that basically says "Show Cs". When the
user clicks it, I run:

Me.Parent.subC.Filter = "[BID] = " & Me![BID]
Me.Parent.subC.FilterOn = True

This works fine, but I don't have a large dataset to test it on yet.
There may end up being 10s - 100s of thousands of records in B and C.

Has anyone had any experience with this sort of situation before? Is
there a better/more standard way of designing an interface that does
this? Will my solution fail horribly at some point?

Thanks in advance,
Luke
 
S

Sharkbyte

Your solution sounds like it should work. As long as your relationships and
indexes are good, you should be fine.

Sharkbyte
 
A

Albert D.Kallal

I like your idea.

For the main a form, and the b form, you just have to set the link
master/child, and it will show ok.

For the b to c, you can put in the link master/child field settings, but you
likely will also need to put a requery event in the b forms on current event
to make the c form follow.

me.Parent.ChildC.Requery

In the link child/master settings for c, you can place:

linkChildFields main_id (whatever is the name of the field in
this sub-form that is used to relate back to the parent table)

LinkMasterFields [MasterForm].[form].[ID] ("masterForm" is the name of
the contorl you used to hold the B form).

I got a number of side by side sub-form screen shots here, and looking at
them might give you some ideas....
 
J

jacket

Albert D.Kallal said:
I like your idea.

For the main a form, and the b form, you just have to set the link
master/child, and it will show ok.

For the b to c, you can put in the link master/child field settings, but you
likely will also need to put a requery event in the b forms on current event
to make the c form follow.

me.Parent.ChildC.Requery

In the link child/master settings for c, you can place:

linkChildFields main_id (whatever is the name of the field in
this sub-form that is used to relate back to the parent table)

LinkMasterFields [MasterForm].[form].[ID] ("masterForm" is the name of
the contorl you used to hold the B form).

I got a number of side by side sub-form screen shots here, and looking at
them might give you some ideas....


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
[email protected]
http://www.members.shaw.ca/AlbertKallal
Click to expand...
 
Top