RE: Normalization was Left AS/400 and Returned

I would probably store the data as warehouse and date, one record for each
shift & day open, or the converse.  If the warehouse was generally a 24/7
operation I would store just closed shift & date I suspect. 
 
---------------------------------
Booth Martin
http://www.martinvt.com
---------------------------------
-------Original Message-------
 
From: Midrange Systems Technical Discussion
Date: 05/04/05 15:17:25
To: 'Midrange Systems Technical Discussion'
Subject: RE: Normalization was Left AS/400 and Returned
 
You would replace a user-editable file with a hard-coded table in a
program?  Ooooooooookay.  That's a... err... UNIQUE solution.  Certainly
one I hadn't thought of.
 
For anyone else, I'll make the question a little more specific: a file
holds maintainable calendar information (let's say for multiple
warehouses), and the information in question is simply a flag that says
whether the warehouse is open that day or not.  The data is stored in a
file because ... well, because that's where everybody except Rob stores
user-modifiable data.
 
Would you store the data one flag per warehouse/date, with the warehouse
and date as the keys to the file, or would you store the information in
an array, perhaps by year or by some other arbitrary unit of time?
 
Joe
 
 
 
> From: rob@xxxxxxxxx
>
> If the only point of the file is two fields:  DayOfYear and Date, then
I'd
> opt to replace the file with a function.
 
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
 
 
.