Field not found lookup error
Nancy Palmquist
nlp at vss3.com
Mon Apr 4 11:51:21 PDT 2011
Richard,
1) Make sure you tokenized the file with the same auto table you will be
using at runtime.
2) Make sure you do not have more than 200 global + user edits.
3) Make sure the tokensize variables are correctly set.
4) Rebuild indexes in logfile
5) Make sure the auto table is properly tokenized.
6) If indexes have large duplication in keys, example, sort on a Y/N
flag and you have thousands of records divided between just a couple of
choices. This can cause problems over a certain number. I found it you
have to do this, purging old data can make the file happy again. PS -
avoid this if possible.
OK Richard - I can try to think of more, if none of these help. Off the
top of my head these are things that can give you the kind of "gotcha"
or a Windows Memory error like you described.
Nancy
On 4/4/2011 1:57 PM, Richard Kreiss wrote:
> I have a routine that posts to a file I call logfile.
>
> This routine has been working fine until today when my client received a
> filed not found error to logfile in index Z. this is a lookup free posting.
>
> I ran the program with the debugger on and did not receive the error. When
> run again with rclerk, the error reoccurred. Run with dclerk, no debugger,
> the program runs fine.
>
> Any suggestions as to when to look for?
>
>
> Richard Kreiss
> GCC Consulting
> rkreiss at gccconsulting.net
>
>
>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
--
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