Selection Logic - Windows 2003 filepro 5.0

[Nancy Palmquist]

Kenneth Brody wrote:
> Quoting Nancy Palmquist (Mon, 02 Apr 2007 15:30:35 -0400):
> [...]
> 
>>We have a scan select process that runs successfully from beginning to
>>end - no errors.  It picks what seems to be the right number of records
>>which it is then supposed to copy to selected files in the output step.
>>I know it picks the right number of records because I count them and
>>display the totals in the @done logic when all is supposed to be done.
> 
> [...]
> 
>>When it breaks I might be missing 3000 records - a significant
>>difference.  We clear the files and run it from the Win2000 and it runs
>>flawlessley with all records copied successfully.
> 
> 
> Any chance of knowing if the records were "missed" on the sort/select
> phase as opposed to the output phase?
> 

The @done logic reported the correct numbers, but the sum of the records 
created demonstrated that some records were not written.  So I have to 
say that since my counts were correct filePro looked at every single 
record it should and that some records were simply not added to the 
files as the programming indicated.

I have never seen filePro do anything like this before and it is very 
troublesome.


> 
>>It has done this twice now.  The process has been running without issue
>>for years and now two months in a row we have had to rerun it repeatedly
>>to get all the records correctly copied.
>>
>>The two computers use the same config file - so index scan is not
>>different.
> 
> 
> If index scan is being used, is it possible that the file and the
> index are being updated while the report is being run, causing the
> index to change during the scan?  Are you using the "-u" flag?

The files are not in use when this is happening.  The right number of 
records are selected and processed. (See note above.)

> 
> 
>>One computer is running Windows2000 and one is running WindowsXP.
>>
>>The switch speed for the WindowsXP is much faster and it is the one that
>>seems to be skipping over records.  Could the switch be dropping packets
>>or something without the OS noticing?
> 
> 
> Not unless something is broken in the network software.

All other reports and processes seem to run without issue.  This is the 
only process that copies a large number of records in one report, 
however.  Most other stuff is data entry and small reports.

> 
> 
>>Does anyone have any notion what we might look for to try to put this
>>process back to working correctly every time?
> 
> 
> Any idea what was different (aside from the missing records) about
> the report on the couple of times it was wrong?

Nothing was changed.  The files were just reset and the process run 
again, from a different workstation.  Otherwise, the programming was not 
altered, the source data was identical (it is not affected by the 
posting process), nothing else except the switch seems to b


> 
> --
> KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
> http://www.hvcomputer.com
> http://www.fileProPlus.com
> 
> 


-- 
Nancy Palmquist 		MOS & filePro Training Available
Virtual Software Systems	Web Based Training and Consulting	
PHONE: (412) 835-9417		   Web site:  http://www.vss3.com