James E. Lang wrote:
> Route Database (Proposed Revision 1)
>
> Overview: A route list will be a set of Transitions and Segments alternating
> with Customers associated with the Segments.
>
> Table Master
> Printer ("color" | "black")
Why do you need a DB Table for this?
> Table: Routes
> Route (e.g.: 26 | 28)
> {key}
> Start (Transitions::Index)
Good.
> Table: Transitions
> Index (To be defined)
> {key}
> FromSegment (nul | Segments::Index)
> {nul only if referenced by Routes::Start}
> FromSegmentDirection ("Ascending" | "Descending")
> ToSegment (nul | Segments::Index)
> {nul only if end of static route}
> ToSegmentDirection ("Ascending" | "Descending")
> Direction (nul | "Left" | "Right" | "Straight" | "U-Turn" | "Cross")
> {nul and "Cross" are used only if the street name remains unchanged}
> {"Straight" is used only if the street name changes}
> Modifier (nul | "Bear" | "Hard")
> {i.e. "Bear Left" or "Hard Right" etc.}
OK.
> Table: Segments
> Index (To be defined)
> {key}
> StreetName (e.g.: "Brentwood" | "Abbeywood")
> StreetPrefix (e.g.: nul | "N" | "E" | "W")
> StreetSuffix (e.g.: nul | "Av" | "Cir")
> EvenSide ("Left" | "Right")
> {The next two fields are needed to compute ordinals in reverse}
> EvenCount (e.g. nul | 0 | 2 | 25)
> OddCount (e.g. nul | 0 | 2 | 25)
Perhaps change to "LastOrdinalEven" and "LastOrdinalOdd"?
> Length (nul | "Short" | "Medium" | "Long" | "VeryLong")
> {Useful for dynamic routing}
> {e.g. "Short" = 1, "Medium" = 3, "Long" = 6, "VeryLong" = 20}
> {I don't like the next four fields but have not found a better way to do it}
> FromRemarkIn (e.g.: nul | "Gate Code: #9630" | "Use key to enter
> building")
> FromRemarkOut (e.g.: nul | "Gate Code: #9630")
> ToRemarkIn (e.g.: nul | "Gate Code: #9630")
> ToRemarkOut (e.g.: nul | "Gate Code: #9630")
Agreed. Please elaborate on when each of these would be used.
Add:
NextTransition (e.g.: nul | Transitions::Index where
Transitions::FromSegment == Index)
{nul if dynamically assigned}
> Table: Customers
> Index (To be defined)
> {key}
> Number (e.g.: 2604 | 2652)
> Unit (e.g.: nul | "A")
> StreetName (e.g.: nul | "Brentwood" | "Abbeywood")
> {nul means look at Segments for this info}
> StreetPrefix (e.g.: nul | "N" | "E" | "W")
> StreetSuffix (e.g.: nul | "Av" | "Cir")
> Segment (Segments::Index)
> SideOverride (nul | "Left" | "Right")
> Schedule (Schedule::Index)
> Status ( "Active" | "Stopped")
> Ordinal (e.g.: nul | 1 | 5 | 19 | "Last" | "Corner")
> Bag ("Yes" | "No")
> Porch ("Yes" | "No")
> Handicapped ("Yes" | "No")
> SatSunonMon ("Yes" | "No")
> Instruct (e.g.: nul | "Del to garage door")
> Landmark (e.g.: nul | "Green Fish MB" | "Past St Light")
> Sequence (e.g.: 7740) {from Arden's database}
> Order
> {used for sorting within a segment}
> {not quite the same as Customers::Sequence}
Also not quite the same thing as Ordinal. :)
Looks good.
> Table: Schedule
> Index {Key} (e.g.: "7DY" | "FSS" | "JJL" | "EX.")
> Display (e.g.: " " | "FSS" | "JJL" | "EX.")
> Publication (e.g.: "LA Times" | "Jewish Journal")
> Mon ("Yes" | "No")
> Tue ("Yes" | "No")
> Wed ("Yes" | "No")
> Thu ("Yes" | "No")
> Fri ("Yes" | "No")
> Sat ("Yes" | "No")
> Sun ("Yes" | "No")
> Color (e.g.: "red")
As before, no problems here.
--
Jonathan "Dataweaver" Lang
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
