Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!usc!sdd.hp.com!hp-pcd!hpcvra.cv.hp.com!rnews!hpcvbbs!akcs.kevin
From: akcs.kevin@hpcvbbs.UUCP (Kevin Jessup)
Newsgroups: comp.sys.handhelds
Subject: Re: help!
Message-ID: <279bad5c:1747.3comp.sys.handhelds;1@hpcvbbs.UUCP>
Date: 22 Jan 91 03:40:06 GMT
References: <7FEEE64EC0001ABE@gacvx1.gac.edu> <2470010@hparc0.HP.COM>
Lines: 22

I am painfully aware of the bug in my CALENDAR program!
 
The original version was posted on the HPBBS for only eight hours
till I discovered the bug myself and deleted the program from the
BBS.  In that eight hour period, someone decided it was worthy of
the goodies disk!  I was also foolish enough to give my home phone
number with the documentation and now get calls at all hours of
the evening.  Anyway, the correct version is on the HPBBS in both
the comp.sys.handhelds conferance and the user.programs conferance.
 
The problem was in the ALMDATE? function as stated above.  Here is
the version I am currently running with no problems...
 
\<< IFERR DUP FINDALARM
THEN DROP2 0 ELSE IF DUP
THEN RCLALARM 1 GET ==
ELSE DROP2 0 END END \>>
 
By the way, the problem occurs in the original version only if you
don't have any alarms set past the month that you are currently
trying to display.  A quick fix would be to set an alarm a good
20 years into the future.