3 tier relationship

[mfstuart]

Hi all,

I need to know how to resolve a relationship/interface problem.

STRUCTURE:

I have 3 Db's that need to be related to one another, where:

A=one to B=many

B=one to C=many

Db A:

ID-A (serial)

Name-A (user input)

Db B:

ID-A (value thru relationship from Db A)

Desc-B (user input)

cID-A.Desc-B (calc=ID-A&Desc-:

Db C:

ID-A.Desc-B (value thru relationship from Db B; cID.Desc-

Desc C (user input)

FORMS:

Db A uses a form to enter records AND a portal to enter Db B records.

That works fine.

Here's the issue - I need the user to enter records into Db C that are related to Db B, on the same form.

SCENARIO:

1. User enters a record for Db A

2. User clicks on portal for Db B and enters a record

3. User then clicks on another portal (Db C) on same form to enter a record relating to Db B.

This relationship from Db A to Db C I can't figure out AND creating records in Db C that are related to Db B.

HELP!

Mark

[Kurt Knippel]

There are 2 simple ways to go about this, both involve the use of the B to C relationship and really disregard the A to B relationship entirely.

The first method is that the button click simply takes the use to a layout in the B file, and they then enter the data for the C records. The layout can look exactly the same or look different, it matters not.

The second method involves the use of a relationship from the A file to the C file via a global which will store the ID from the selected B record. When the user clicks on the B record, the ID is stored in the global, which will in turn activate the relationship from B to C, which is simply occupying space in the A file.

The first method is more work to implement, but is a cleaner solution and is much more logical. The second method is a bit confusing if you come back for more development, but it pretty easy to setup.