windows error

[charles day]

Kenneth Brody wrote:

>charles day wrote:
>  
>
>>Nancy Palmquist wrote:
>>    
>>
>[...]
>  
>
>>>If you have variables that are undefined, using aa instead of aa(8,.0)
>>>for example.  Each record that needs to assign a value to aa will use
>>>a new memory location.  So eventually you will exceed the memory
>>>available.  This is noticed on a report where it crashes at about the
>>>same number of records but not a specific record.  Or a long data
>>>entry session that is never closed and does this kind of thing.
>>>
>>>      
>>>
>>Nancy,  Thanks.
>>
>>If in this case, undefined variables are eating memory, then you have
>>hit the jackpot with your suggestion. I have 18 in the input table and
>>    
>>
>[...]
>
>Assigning a new value to an uncast dummy field will not eat up all available
>memory.  If new memory needs to be allocated to hold the field, the old
>memory is freed and can be reused.
>
>  
>
The error message received today is:

instruction @ 00483160
referenced memory @ 003f800
the memory could not be read from.

I can not determine when it happened in theprocessing table without 
going there to see what files did and did not get data posted to them. 

Any ideas are appreciated.

Charles Day
does this tell anything?