Puzzler of the day - 5.0 Windows Setup

Nancy Palmquist nlp at vss3.com
Tue May 3 13:49:19 PDT 2011


Windows clients are all XP.  Server is WIN2007.  Filepro is Lan version 
5.0 for Windows.

I have a stumper that I wonder if anyone else has run across.  Maybe 
this will be informative.  I like to post these things so others might 
find information in my stumbling.

Running a billing that generates statements for different accounts 
printing details from a file.

We tested this from three computers on the network.  Computer A (client 
machine worked fine), Computer B (client machine broken), Computer C 
(Network Server running Win2007 worked fine).  They do use different 
config tables but the differences are in printers only.  All the other 
variables are the same - double checked.

Here is the problem:

command line:

/fp/dreport monthbill -f billrept-nan -v billreptv -s -rx Y -u -pq -md

Selected using a selection set all transactions for billing account 
05502 to 05683.  Some billing account may have profit centers or sub 
accounts, but that just affects the secondary sort.

Output does a page feed by billing account / account.

When it is broken, here is what I get.  Output prints two lines for each 
record (doubling the statement balance) and it starts the output at 
billing account 05575 instead of 05502 (all data before 05575 is gone).

I turned off Index Scan - still broken on Computer B.
I rebuilt all the indexes, not change.
I added -o9 to the menu and looked at the index created and the index 
reflects exactly what printed.  It starts at account 05575 and has each 
record twice.  So the output from before 05575 was not even generated, 
since it was not even in the index.

Now if I have Computer B, run from 05502 to 05574 - it works correctly.
If I have Computer B, run from 05576 to 05683 - it works correctly.
If I have Computer B, run just 05575 - it works correctly.

I do not use lookup (dash) in the programming so I am not roaming 
around.  I do use the PRINT command but that would not cause the index 
to include the duplicate records since that happens on the generating 
side not sort/select side.

To my experience, I can say SELECT - 20 times in a scan table and I 
still only get one selection.  But just to make sure, I did check and I 
only issue the SELECT command once, without condition, so it is not 
repeating that.

BTW - No associated fields are used in this file.  Eliminate that 
possibility.

I know this is not the current version and since we only have one 
computer out of three that will not process this file correctly, I can 
not see that this is a re-creatable setup.

Well we decided to change the location of the employee to use the Server 
to run this output, instead of the Computer B that will not select/sort 
the data correctly.

This was just for your amusement and maybe it will offer someone an AHHA 
moment with one of your issues.

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



More information about the Filepro-list mailing list