FW: Reading keys stops

[Scott Walker]

-----Original Message-----
From: Scott Walker [mailto:scottwalker at ramsystemscorp.com] 
Sent: Thursday, December 1, 2016 12:06 PM
To: 'Filepro List' <filepro-list at celestial.com>
Subject: RE: Reading keys stops



-----Original Message-----
From: Filepro-list
[mailto:filepro-list-bounces+scottwalker=ramsystemscorp.com at lists.celestial.
com] On Behalf Of Kenneth Brody via Filepro-list
Sent: Thursday, December 1, 2016 10:29 AM
To: Richard Kreiss <rkreiss at verizon.net>; 'Richard Kreiss'
<rkreiss at gccconsulting.net>; 'Filepro List' <filepro-list at celestial.com>
Subject: Re: Reading keys stops

On 12/1/2016 9:44 AM, Richard Kreiss via Filepro-list wrote:
> Solved this problem this morning.
>
> The selection program uses a date field as part of the selection criteria.
> There were 2 records which had incorrect dates entered - too far out 
> (01/22/2216).  That date should have been 12/02/2016).
>
> I will need to add a check for this date when manually entered or changed.
> This is normally a calculated date as the last day of the month prior 
> to the due date.
>
> After correcting the 2 records with improper dates, the program ran.
>
> Thank you to those who responded with other possible solutions.  Those 
> suggestion were well thought out and I need ot keep them in mind when 
> checking for solutions to other problems.

Why would a date "too far out" cause your processing to "hang"?

--
Kenneth Brody


Ken,

Maybe he means "it appears to hang" when in reality if he ran the debugger,
it would show things were humming along, but in a circular fashion (endless
loop :-) )

I've had instances when I use "lookup -" with an index built on a date, like
Order Date.  In the routine, after we have gotten to the records that are
PAST the date range we want, we use a lookup -  with -el flag,  to some very
far away date, like "12/31/40".  This should quickly get us to the last
record in the index.  If however, someone had entered a record with the date
of "12/31/46" instead of "12/31/16", it would get us into an endless loop.

I hope I have explained this clearly.

Regards,
Scott
  
_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
Subscribe/Unsubscribe/Subscription Changes
http://mailman.celestial.com/mailman/listinfo/filepro-list