> Explanation 2 seems very plausible and will have to try it next time my > client runs into this problem. As I indicated, it happens sporadically and > rebooting the computer seems to solve the problem.
I would look for: 1. Anything running at those sporadic times that might be slowing R:Base down to a crawl and making the reports timeout. 2. Anything else that might have run before you have the problem that would be lowering the timeout setting (or even setting it to 0). To test for this, you could direct the output of the CAPTURE /? command to a text file before every printing of the report. When you have the problem, check that file to see what the timeout was when the problem occured. I'll be you find it has been reset. -- Larry ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
