Hi Irv,

>I think the native Fox controls should be more efficient than the Richtext, but one question...Why are you writing this log to the Server? Could it be written to a local machine's C:-drive, maybe this would be a distribution of labor that would be beneficial...
>
>-Irv.
>

The server app writes to the log as soon as it processes a request from any of the workstations. Would it be faster if it has write it to a file not located locally (in the server PC)? Wouldn't it contribute to the network traffic?

Thanks Irv! =)

>*********
>
>>Hi Irv!
>>
>>>David has a good idea; I use something similar to read and present/edit the contents of text files using StrtoFile() and FiletoStr() and a regular EditBox. I know you have huge volume but how long a history do you need to keep? Can you create some sort of ongoing Purge process?
>>
>>I actually am using STRTOFILE() to save it to a text file and at the same time output same string to the Richtext control. I noticed that when about 5,000 lines are written to the control, our NT server (512MB RAM) just freezes up and gives a message like 'running low on resources'. Checking on Task Manager, I find out that Memory Usage has overshot its maximum level!
>>
>>I then removed the Richtext control from my server app and the system just worked perfectly!
>>
>>The system processes around 12,000 request per hour for 8 hours. That's about 96,000 for the day. After the day, we do not need to save the Richtext contents since I have already STRTOFILE()d it.
>>
>>Would either using an EDITBOX or a GRID control to display the activity log not suffer the same fate (running low on resources) considering the volume of requests?
>>
>>Thanks to you all! God bless...