windows error

[charles day]

Nancy Palmquist wrote:

> charles day wrote:
>
>> running fp 5.0  on  XP networked to a cpu running '98.
>>
>> Customer occasionally gets an error message. The processing will run 
>> sometimes for days without the error, then the error will occur.  
>> Customer  X's   the XP window,  then goes back into filePro and the 
>> error will not necessarily occur the next time the process is run and 
>> may not occur for days again.
>>
>> message to the effect:
>>
>> instruction @ blah-blah-blah can not be read
>>
>> what does this have to do with filePro code and how can I find out 
>> where and why windows is having a fit?
>> what should I look for  in  filePro  code or settings that might 
>> cause this or allow it to happen?
>
>
> If the data can be processed without error after the XP is rebooted, 
> and this only happens after many days of use and not at the same spot 
> in the data or programming, it seems unlikely that it is filePro, 
> however, here are some things I learned.
>
> 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 
39 in the auto table.  All in the input table are assigned the value of 
a particular field such as  aa=49 .   Those in the auto table are 
assigned values such as  ze="Press R for a repair" and ze us used in an 
input popup with a couple other selections.  I will define them as see 
what happens.

> This is more likely to be the case with Windows98 because of 
> differences in the Operating system that had memory leaks that could 
> not be plugged and resources could easily be overtaxed.
>
> I would never use an XP client to a Win98 server.  I don;t thing this 
> should even work.  We had all kinds of issues when I had a few 
> customers try that.  Always use the newest OS for the server, it will 
> be able to handle the slower clients but I can't imagine the Win98 
> being able to handle the XP client well.
>
> Well I don;t know if that helps but good luck.  Reboot the server and 
> client frequently  to reset all the memory issues and see if that helps.


Customer shuts down every night and boots again in the morning.

Charles Day