Yep, I avoid while loops like the plague, but I'll check again. They tend to sneak in!
Thanks, I haven't much more hair to lose <grin> _____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Sami Aaron Sent: Tuesday, January 30, 2007 9:50 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: RBDOS disappearing Dennis - I remember some problems with long and/or nested WHILE loops when users started using Windows 2000. Check the R:BASE cfg FILES settings as well as the Windows Files setting. I also remember changing WHILE loops to GOTO loops and that worked in some instances. Good luck! Sami _____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Dennis McGrath Sent: Tuesday, January 30, 2007 9:24 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: RBDOS disappearing Larry, I'm going to RSTYLE all the code the next time I can get exclusive access. While I'm sure all of it is clean, this something I do periodically just to assure I haven't missed anything. It is only certain PC's that have the most problems. We are looking at the most problematic computer now. Some users run the same routines with no problems. I may have to resort to that incredibly ancient method of code testing that you describe!!! It was on my list of things to try. Thanks, Dennis _____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Lawrence Lustig Sent: Monday, January 29, 2007 9:59 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: RBDOS disappearing At the risk of sounding silly (but not intending to): have you RStyled the code? I think you have some odd memory related problem that only presents itself on certain DOS setups. Have you determined that the point of failure is in the same routine on each PC? If so, and you can't trace to it, you may need to insert numerous OUTPUT Logfile.TXT APPEND; WRITE 'I''m here'; OUT SCREEN lines into the program to figure out _where_ you are bombing out. -- Larry
