Jan, The other thing that affects form linking is the Table Relations tab, in the Form Settings. Even if your hierarchy isn't strict in enforcing ordinary PKs and FKs, switching to "many to many" might make your form start working. This tends to be the right choice for the "tree" structure, one-to-many for the "chain" structure.
Bill On Tue, Mar 19, 2013 at 3:33 PM, Bill Downall < [email protected]> wrote: > Oops. Can't to Ctrl-Enter in email to put a plus sign and continue on the > next line. Starting over: > > Here's a simple 3-table hierarchy: > > CREATE TABLE Customers + > (CustomerID INTEGER NOT NULL PRIMARY KEY, + > CustomerName TEXT(48) NOT NULL + > ) > > CREATE TABLE Orders + > (OrderNumber INTEGER NOT NULL PRIMARY KEY, + > CustomerID INTEGER NOT NULL REF Customers (CustomerID), + > OrderDate DATE NOT NULL + > ) > > CREATE TABLE LineItems + > LineItemID INTEGER NOT NULL PRIMARY KEY, + > OrderNumber INTEGER NOT NULL REF Orders (OrderNumber), + > ItemSKU TEXT(48) NOT NULL, + > ItemQuantity INTEGER, + > ItemPrice DOUBLE + > ) > > AUTONUM CustomerID IN Customers USING 1001,1 > AUTONUM OrderNumber IN Orders USING 100001,1 > AUTONUM LineItemID IN LineItems USING 1,1 > > > On Tue, Mar 19, 2013 at 3:28 PM, Bill Downall < > [email protected]> wrote: > >> Here's a simple 3-table hierarchy: >> >> CREATE TABLE Customers (CustomerID NOT NULL >> > > >
