|
We've come up with 2 alternatives for trip itinerary records and would
like to settle on one or the other:
Option 1: delineate one row for each "stop" in the route:
Surrogate_Key.
Location_ID (refers to a row in "location file").
Arrival_Date.
Arrival_Time.
Number_Of_Minutes_At_This_Stop.
Three (3) rows would be required to delineate the "steps" to a single
destination and back. Some users prefer this type of listing on screens.
Option 2: delineate one row for each "from" and "to" location in the route:
Surrogate_Key_Value.
From_Location_ID (refers to a row in "location file").
From_Location_Departure_Date.
From_Location_Departure_Time.
To_Location_ID (refers to a row in "location file").
To_Location_Arrival_Date.
To_Location_Arrival_Time.
Two (2) rows would be required to delineate the "steps" to a single
destination and back. Some users prefer this type of listing on screens.
How should we settle this debate?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.