Dan,

I use unbound forms and variable listviews to accomplish that.
1 workorder can have many parts, many standards, many documents.

Jan
 


-----Original Message-----
From: "Dan Goldberg" <[email protected]>
To: [email protected] (RBASE-L Mailing List)
Date: Thu, 27 Oct 2011 15:30:57 -0700
Subject: [RBASE-L] - Re: one to many to many


Thanks Bernie. I got the tables set but I am drawing a blank on how to 
structure it in a form.
 
Dan
 
 
From: [email protected] 
Sent: Thursday, October 27, 2011 3:22 PM
To: RBASE-L Mailing List 
Subject: [RBASE-L] - Re: one to many to many
The repairs table would be a region with the key to the header table.
The Parts table would be a separate region with the key to the Repairs 
table.
 
Good luck,
Bernie Lis





From: "Dan Goldberg" <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Thursday, October 27, 2011 6:12:49 PM
Subject: [RBASE-L] - one to many to many


I have a work order. Each work order has many repairs. Each repair has many 
parts.
 
Header Table – One
   Repairs Table – Many repairs to one header
       Parts Table – Many parts to each Repair
 
I know I can do a one to many form but how do I create a form based on one 
to many to many?
 
If anyone has any ideas let me know. It would be appreciated!!
 
TIA
 
 
Dan Goldberg

Reply via email to