Many to One logic changes in business flow

[Guest]

I need help in defining the logic on this busines flow:

Invenory arrives on a INBOUND TRUCK and is documented on the Inbound Form as
ONE TRUCK ID to MANY BOXES of inventory. Included in the table is the
Destination ID as to where the inventory is going.

Once the inventory is unloaded .... we no longer care about the TRUCK ID.
The boxes of inventory are divided and put onto a differernt truck to go to
various destinations. On the Outbound From, we need to track each (One)
destination to many Boxes.

There are fields from the Inbound Form that needs to be transferred to the
Outbound field.

INBOUND: Truck ID ------ BoxIDs :
fields on MAIN form (TruckID, Ship Date) (ONE)
fields on SUBFORM (destination ID) (MANY)


OUTBOUND: DestinationID ----------BoxIDs

Transfer fields from INBOUND to OUTBOUND form and change the ONE to MANY
logic from the Truck ID to the Destination ID

Thanks.....

 

[Guest]

I think you need to define the high-level purpose of this application. What
are you tracking? What is important, trucks, boxes or destinations. Do you
care about what happens after the outbound trucks leave? Do you have to track
their arrival? The underlying storage mechanism is tables not forms, so you
need to design a table structure that can support your requirements. I would
not even think about forms until you have come up with the data model for the
tables.
It seems you might need:
Truck table:-
-- Truck ID
Origin table:-
-- Where trucks come from
Destination table:-
-- Where trucks go to
Delivery table:-
-- Delivery ID
-- Truck ID
-- Origin ID
-- Destination ID
-- Status (In transit or Arrived)
Load table:-
-- Delivery ID
-- Box ID

For inbound and outbound you just change the origin and destination in the
Delivery table.

Dorian

 

[Guest]

High Level:

I understand that "form" may not be included in the logic at this point,
however, uderstanding the use of the forms may help you understand the
underlying logic.

The Inbound Truck pulls into the warehouse. The inventory is checked off
and then separated. An outbound truck going to a specific destination is
loaded with boxes. The boxes may be from several trucks.

The information retrieved from the Inbound truck (Inbound Form) for each
package is the vendor name, the wieght of the package, the PO# for the box
and the ship date. The information from the inbounnd truck will be typed
into Access manually by an admin.

This information as well as additional information is also needed for the
Outbound form which will be sorted and produced automatically by Access. The
date and destination will be the unique keys for the outbound form.

 

[Guest]

It doesn't matter where the truck came from.

 

[John Vinson]

I need help in defining the logic on this busines flow:

Invenory arrives on a INBOUND TRUCK and is documented on the Inbound Form as
ONE TRUCK ID to MANY BOXES of inventory. Included in the table is the
Destination ID as to where the inventory is going.

Once the inventory is unloaded .... we no longer care about the TRUCK ID.
The boxes of inventory are divided and put onto a differernt truck to go to
various destinations. On the Outbound From, we need to track each (One)
destination to many Boxes.

There are fields from the Inbound Form that needs to be transferred to the
Outbound field.

INBOUND: Truck ID ------ BoxIDs :
fields on MAIN form (TruckID, Ship Date) (ONE)
fields on SUBFORM (destination ID) (MANY)


OUTBOUND: DestinationID ----------BoxIDs

I think the problem is that you're modeling a Many to Many
relationship as a Many to One.

One Truck may have many boxes.
Each Box will be on many (well, two anyway) trucks.

Consider a structure like:

Boxes
BoxID
DestinationID <where this box should end up>
<attributes of the box>

Trucks
TruckID

Loads <the many to many resolver table>
BoxID <which box are you considering>
TruckID <which truck is it on>
InOut <1-byte Text field, I for inbound, O for outbound>

John W. Vinson[MVP]

 

[Guest]

Using my tables as an example:
When a truck arrives, a Delivery Table record is created also multiple Load
Table records are created, one for each box on the truck. For each outgoing
truck, a Delivery Table record is created, also a Load Table record for each
box on the truck.
Using this structure you can select the boxes to go out from a list which
would include only boxes that have arrived but have not yet left.
All you need to do is to expand the tables to include your additional data
like vendor ID, ship date, box weight, etc. Then you need to come up with
forms to manipulate the data.

Dorian