Problem with dreport crashing

[Nancy Palmquist]

Bruce Easton wrote:
> Nancy Palmquist wrote Thursday, July 31, 2008 4:37 PM:
>
> [a bunch of good stuff about things to watch out for 
> on Windows with filepro (if rats were filepro 
> developers, they would be eating their young at 
> this point), including ..]
>   
>> Then I increased the TOK size for all TOK levels, that put me up to 
>> 99.9% reliability. 
>>
>>     
> [and ..]
>
>   
>> 2) Check TOK sizes - increase if not sure.  defaults are 20000 for each 
>> of the three types.
>>
>>     
>
> I was a bit surprised when I ran that little test a while
> ago (Unix fp 5.0.14) where it said at runtime my token table 
> for the called table was too small when all it had in it was:
>
> ::1="333":
> ::write:
> ::end:
>
> (field 1 was a ten character field and the map only had 
> that one field in it; also only one index for the file 
> against that one field)
>
> Isn't there a minimum tok size for form/called prc 
> in use if not set?
>   

Default is 20000.  You can decrease to 10000. Tok size is not a measure 
of the size of the processing only, in includes arrays and variables.  
Is it possible the machine did not have enough memory to allocate the 
minimum?  Tok size might be for automatic processing, input processing 
or form processing (calls are using the same memory as forms, chains use 
the same memory as input or output.)  When you are Requesting Output the 
form processing is the same as INPUT and the calls use the form 
processing.  So is it possible that the automatic processing was the 
issue or a form that printed.

Nancy

> Bruce
>
> Bruce Easton
> STN, Inc.
>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> 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