Too many years ago I had some similar issues with someone wanting reports to
be run on odds days and often using either RPG or Query/400.
I ended up resorting to writing a program that ran every night to update a
calendar file which contained a variety of date information and flags that
could be set to control situations.
Running the job every night set the look-ahead dates and prepared the file
for any automatic or manual settings that needed to be made.
The beauty of do this was that it worked for allowing date selections within
query which were quite painful at the time but it also worked for the odd
days and dates that were requested from time to time.
You may need to resort to the same type of calendar file (with appropriate
documentation and maintainability).
Sometimes an algorithm is just not going to work.
Norm Dennis
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of McKown, John
Sent: Friday, 12 December 2008 12:50 AM
To: Midrange Systems Technical Discussion
Subject: RE: Week of the month
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Shannon ODonnell
Sent: Thursday, December 11, 2008 9:34 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Week of the month
I haven't been reading every post on this one (so many!) but
the first thing
that popped into my head was that, with all the work you are
putting in on
this, trying to come up with the perfect algorithm... you
could probably
create your own "Number of Week" database for the next 10
years, keying it
in manually, in less time than it will take to test and
perfect this "day of
week" algorithm.
I guess it depends on whether you are most interested in
solving the problem
in a timely manner or doing it for the sheer fun of figuring out the
solution programmatically.
Sounds like a programmer I knew long ago. She didn't want to bother
writing a leap year algorithm in COBOL (in the 1970s). So she simply
hard coded the leap years into a table. She hard coded up to her
retirement year. She figured that after that it would be somebody else's
problem. <grin>
--
John McKown
Systems Engineer IV
IT
Administrative Services Group
HealthMarkets(r)
Administrative Services Group
9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * (817)-961-6183 cell
john.mckown@xxxxxxxxxxxxxxxxx * www.HealthMarkets.com
Confidentiality Notice: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential or proprietary information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message.
--
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.
No virus found in this incoming message.
Checked by AVG -
http://www.avg.com
Version: 8.0.176 / Virus Database: 270.9.16/1841 - Release Date: 12/15/2008
9:01 AM
midrange.com
