I have read (re: index resync error) that it is best to use a form based on a set solely for the purpose of display and navigation and that data entry and editing is best done by popping up separate forms based on the target tables. Does this mean for a parent and child table with a one to many relationship that I would have to create a button on my main display/navigation form to call up a form designed for the entry/editing of the parent table and another button to call up a form designed for the entry and editing of each child item? I find the process rather clumsy but a solid app wins over a shaky one.
I'd like to get this clear before I get myself in mega trouble. Currently I have an invoicing application built primarily around what could be a "complex set". I don't know if it is or what I am setting myself up for.
The parent table is Sales_order two child tables, salesord_trans and invoices are linked one to many to the parent. The invoices table is linked one to many to a child invoice_detail. The idea is that sales orders are made by the sales staff and each item sold is entered into the salesord_trans table. As we send out batches of items sold we generate invoices by posting the records from the salesord_trans table to the invoice_detail table.
The interface design is based on a 2 tabbed form. the first tab contains the Sales_order table and a browse containing the salesord_trans table. The second tab contains the invoice table and its invoice_detail child.
The design can go one way or the other at this moment and I can use any bit of wisdom people can offer at this point. Thanks in advance.
I'd like to get this clear before I get myself in mega trouble. Currently I have an invoicing application built primarily around what could be a "complex set". I don't know if it is or what I am setting myself up for.
The parent table is Sales_order two child tables, salesord_trans and invoices are linked one to many to the parent. The invoices table is linked one to many to a child invoice_detail. The idea is that sales orders are made by the sales staff and each item sold is entered into the salesord_trans table. As we send out batches of items sold we generate invoices by posting the records from the salesord_trans table to the invoice_detail table.
The interface design is based on a 2 tabbed form. the first tab contains the Sales_order table and a browse containing the salesord_trans table. The second tab contains the invoice table and its invoice_detail child.
The design can go one way or the other at this moment and I can use any bit of wisdom people can offer at this point. Thanks in advance.
Comment