***segmentation violation Press Enter to continue:
daN baueR
dan at onlinemgt.com
Tue Feb 15 08:52:46 PST 2011
Thanks for the suggestion. I''l try that next.
On Mon, Feb 14, 2011 at 9:54 PM, Jeff Harrison <jeffaharrison at yahoo.com> wrote:
> ----- Original Message ----
>
>> From: daN baueR <dan at onlinemgt.com>
>> To: FilePro Mailing List <filepro-list at lists.celestial.com>
>> Sent: Mon, February 14, 2011 2:18:03 PM
>> Subject: ***segmentation violation Press Enter to continue:
>>
>> I hope someone can let me know what this would be referring to. I'm
>> running a very simple report to check on some irregularities.
>> Basically I'm importing data into my main working file. This report
>> runs from the importing file. All the records in the import file are
>> stored permanently. In it I store the @RN of the record in the main
>> working file that each import record was posted to. Some records are
>> showing up that don't match the saved @RN in import file. There is
>> also an client file number stored for each record that is not unique
>> but there are only a few matches for this number. This report was
>> created to try and track down discrepancies.
>>
>> This is the output table
>> ::oa=""; ob=""; oc(8,.0)=16:
>> ::lookup ppp = process R=oc -B:
>> :not ppp:end:
>> badrec:ppp(65) ne 23:ob="NO":
>> :badrec:gosub findit:
>> ::end:
>> findit::lookup ccc = process K=23 i=D -bx:
>> loopa:not ccc:return:
>> :ccc(65) ne 23:return:
>> ::oa=oa<ccc(@rn); getnext ccc; goto loopa:
>>
>> importfile
>> field 16 saved @RN of main file
>> field 23 account number
>>
>> process file
>> index D client file # built on field 65
>>
>> I'm using a -V table to narrow the report down to only problem
>> records. The report selects records and then gets stuck in the same
>> place. I'm printing the report to the screen so I can at least see the
>> first couple of pages print correctly and then I get the error
>> message. Thanks for your help.
>>
>> Dan Bauer
>> dan at onlinemgt.com
>> _______________________________________________
>
> Dan, from your description it sounds like you may have a bad index D. Have you
> tried rebuilding this index and running the process again?
>
> Jeff Harrison
> jeffaharrison at yahoo.com
> Author of JHExport and JHImport.
>
>
>
>
>
More information about the Filepro-list
mailing list