If one shuttle can have more than one driver, why do you store driver
information in the shuttle record? That would mean that a shuttle can only
have one driver, the one in the record, and driver.db just stores
additional info about that driver.

And if there is only one driver per shuttle, why would you want to display
a tableframe of drivers who *aren't* assigned to the shuttle?

HOWEVER, if shuttle:drivers is 1:M, then shuttle.db should contain no
driver info at all. Drivers.db would be indexed on shuttleID AND driverID
-- and this should allow you to display two table frames.

THIRD POSSIBILITY: If shuttles:drivers is M:M you need a linking table with
two fields: shuttleID and driverID. Call it (say) link.db. Now you can show
all the drivers assigned to a shuttle by linking
shuttle.db:link.db:driver.db
and you can show all the shuttles assigned to a driver by linking
driver.db:link.db:shuttle.db.

--
Jim Hargan


On Fri, 15 Aug 2008 12:29:53 -0700, Pete Gerhard wrote:

> Okay,
>
> I add a field to Drivers = "DriverID" and and Index "DriverID" on
> "DriverID" and add field "DriverID" to Shuttle.db.
>
> Now if I join on "DriverID" all works perfectly. This is the index that
> had been broken because I eliminated the fields DriverID and used "Last
> Name" + "First Name" as the key in Drivers.db.
>
> When I join this way I get a one-to-many from Shuttles to Drivers.
> When I join the other way on last and first names, I get a one-to-one.
> And apparently a one-to-one won't allow me to have a table frame
> (multiple-row) for each table, only the master/parent.
>
> But I want two tableframes because I like the "table-look" of the
> tableframe over just a bunch of fields. The Headings are nice and neat.
> If I have to create that look by just adding stray fields together, I
> don't even think I can get there. Way too much work anyway.
>
> Any help?
>
> Pete
>
> From: Pete Gerhard on 8/15/2008 11:36 AM:
>>
>> Let me summarize what I wrote below:
>> I want two tableframes (i.e. multiple rows format) on my form.
>> I can't get two when I link as I want to. One of them is undefinable.
>> I CAN have a tableframe for the master and independent fields for the
>> detail table, but not two tableframes as I desire.
>>
>> Thanks,
>> Pete
>>
>> From: Pete Gerhard on 8/15/2008 10:26 AM:
>>>
>>> Friends,
>>>
>>> I am trying something really simple and can't get it to work. I'm
>>> missing something very basic it seems. I am a power user and have been
>>> using paradox for years.
>>>
>>> Trying to link (for airport shuttles):
>>> (Parent Table)
>>> Shuttles.db with "Shuttle Code" as Key.
>>> Includes "Last Name" and "First Name" fields for the driver.
>>>
>>> with
>>> (Detail Table)
>>> Drivers.db with "Last Name then First Name as Key.
>>>
>>> I want to link these on "Last Name" & "First Name" so there is a
>>> one-to-one relationship.
>>>
>>> I also want to have two table frames on my form, one for each table.
>>>
>>> If I only link on "Last Name", all is fine. If I link with both "Last
>>> Name" and "First Name" I cannot define fields in Shuttles' table frame.
>>>
>>> I actually got this to work but changed something along the way in one
>>> of the two tables (i.e. restructuring). When I open that form I get a
>>> message that it can't open Drivers since an index is missing. I open
>>> anyway and get all to work (i.e. two table frames that behave
>>> properly). But if in trying to deal with the index problem, I go into
>>> design, unlink drivers and relink it, or remove and reinstall the
>>> table and relink it, fields become undefined.
>>>
>>> Help!
>>>
>>> Pete
>>>
>>