Reading keys stops

[Richard Kreiss]

The year that was causing the problem was 2216.  Not sure if this is a valid date even though it passes the date edit. 

Richard
Sent from my iPhone

> 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.
> 
> Richard Kreiss
> 
> -----Original Message-----
> From: Filepro-list
> [mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On
> Behalf Of Richard Kreiss via Filepro-list
> Sent: Thursday, December 1, 2016 7:58 AM
> To: Filepro List <filepro-list at celestial.com>
> Subject: Re: Reading keys stops
> 
> Will check. 
> 
> Problem may be a bad record added after the output on Monday. 
> 
> Based on where the output stops, the records were selected and were being
> indexed for the run. This is a process that creates an HTML file for each
> record selected. The HTML is then transmitted elsewhere for processing. 
> 
> Richard
> 
> Richard
> Sent from my iPhone
> 
>> On Nov 30, 2016, at 11:19 PM, ken white <kenwhite at verizon.net> wrote:
>> 
>> I would try a chkdsk.  If a bad disk drive or filesystem is suspect (and
> you have the space) then rename key to bkup and copy bkup to key.
>> When the selection set ran, was it a pure scan or a -j scan ?    If a -j
> scan then I would suspect bad data which is included in the index.
>> Does the lookup - use a global flag so that it executes only once ?
>> 
>> 
>> 
>> -----Original Message----- From: Richard Kreiss via Filepro-list
>> Sent: Wednesday, November 30, 2016 10:24 PM
>> To: Filepro 2 List
>> Subject: Reading keys stops
>> 
>> Client called and advised that an output which worked yesterday does not
> run today.
>> 
>> Windows server 2012
>> Windows 7
>> 
>> The output uses -v select processing and a - lookup. They rebuilt all of
> the files auto indexes after running freechn. They also did a system reboot.
>> 
>> The transition action file has over 300,000 records.
>> 
>> Any suggestions as to what may be causing this output to stop will be
> appreciated.
>> 
>> Also, a selection set was created to select the records similar to the
> select processing and this stopped also.
>> 
>> Richard
>> Sent from my iPhone
>> _______________________________________________
>> Filepro-list mailing list
>> Filepro-list at lists.celestial.com
>> Subscribe/Unsubscribe/Subscription Changes 
>> http://mailman.celestial.com/mailman/listinfo/filepro-list
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list