Reading keys stops

[Kenneth Brody]

On 12/1/2016 12:49 PM, Richard Kreiss via Filepro-list wrote:
> The year that was causing the problem was 2216.  Not sure if this is a valid date even though it passes the date edit.

It's a perfectly valid date.  (Why wouldn't it be?)

Since we know nothing about your processing, we can't give any advice on why 
that date was a problem for your processing.

>> On Dec 1, 2016, at 9:44 AM, Richard Kreiss via Filepro-list <filepro-list at lists.celestial.com> 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.
[...]

-- 
Kenneth Brody