|
> From: James Rich > > > 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? > > Neither. I'd find out what the rules are for when it is open/closed and > code those rules. No file/table needed. In fact, I've already done this. There are no hard and fast rules, James, that's the point of a maintainable file. Some warehouses are open 24/7. Some are open based on available labor, or on inventory movement. Some are available M-F, some Saturday. Some are seasonal. Some are not open on certain legal holidays. Some are open when the tide is high. Which are open when is subject to change on a monthly, weekly or even daily basis. Coding every possible rule would be counterproductive, especially since it could not handle the ad hoc changes. A table could just as easily summarize those rules. Joe
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.