Create a Header Entry Form then Move to the Details form based on the ID from the Header From

[MBFromIT]

Trying to create a PO Entry From. So there is a PO Table and then a Table for each ITEM linked on a POID.

So I want to enter the PO, then do some form validation before close the form and moving to the entry of the PO ITEMS.

So I would think I would need the PO Entry Form then using the new POID open the ITEM Form and move to the
same record just entered and then continue entering the ITEMS for the new PO.

This seems to be a VERY common problem. That is having a Header and Details table and needing to enter the Header and then Details info.

Any design pattern for this?



Thanks!

[ssanfu]

Welcome to the forum.

So I would think I would need the PO Entry Form then using the new POID open the ITEM Form and move to the
same record just entered and then continue entering the ITEMS for the new PO.

Consider using a main form, "frmPO_Entry", with a sub form "sfPO_Detail".
Enter the data for the PO in the main form, then enter the items in the sub form. So only two tables at this point - "tblPO" and "tblPO_Details".

Maybe a table "tblPO_Items".... you haven't provided any details about your dB, table structures or relationships


Good luck with your project........

[ranman256]

you can do all this in 1 parent/child form.
the parent would be the PO MASTER,
then the subform would hold the items, just enter them.

[Missinglinq]

Here's a simplified example I ran up for somebody, a while back, for what you're talking about. It starts with a Customer Table, which would be one step up in the hierarchy, above your PO Table, which you may or may not need, where customers can place multiple orders, and each order can have multiple items:

CustomerTable
CustomerID 'Primary Key
CustomerFirstName
CustomerLastName
CustomerHomePhone
Customer CellPhone
CustomerStreetAddress
CustomerCity
CustomerPostalCode
...and so forth

OrdersTable
OrdersID 'Primary Key
CustomerID 'Foreign Key
OrderDate
MethodOfPayment
...and so forth

OrderItemsTable
OrderItemsID 'Primary Key
OrdersID 'Foreign Key
ItemName
ItemQuantity
ItemCostPerUnit
...and so forth

Notice that the Tables 'cascade'

• The Primary Key of the first Table becomes the Foreign Key of the second Table
• The Primary Key of the second Table then becomes the Foreign Key of the third Table

To display all of these in one Form and to be able to enter New Records or Edit Existing Records in all of these Tables:

• The Main Form would be based on the CustomerTable
• The first Subform would be based on the OrdersTable and linked to the Main Form by the CustomerID
• The second Subform would be based on the OrderItemsTable and linked to the first Subform by the OrdersID

Even if you don't need the Customers Table, this should point the way for you.

Linq ;0)>