Rich: I had a rash of problems like this several months back. It was driving me crazy! I made a number of changes and enhancements that ultimately eliminated the problem. R:Base is running smooth as butter now.
I would suggest that you carefully inspect each R:Base script/program that is involved in this process. In my instance I had a command file that had the notorious hanging continuation character. A line of code ended with a plus sign (+) that was not needed. Use R:Code to check your programs. Note that R:Code is not a compiler and it will not catch the hanging continuation problem but you may be surprised to find some hard-to-find coding errors. I have also greatly reduced my use of temporary tables. A comment was made some time back to the effect that temporary tables do not handle indexes well. I have cleaned up my code considerably. I create and type each variable very explicitly and then I clear them once they're not needed. Make sure you are not attempting to use a variable or redefining a variable to an incompatible type depending on how it's being used. Review the rules for WHILE loops and using cursors if you use them. Beyond that make sure you have the latest service packs for all software. Service Pack 4 was just released for Windows 2000. Another thing that may have been causing me problems was a known conflict between Norton Antivirus and the Adobe Distiller software. Here again make sure you are using the latest versions/patches/fixes. This goes both for the Norton product and the Adobe software. Others will probably chime in with other suggestions but I can tell you from my own experience that I have eliminated nearly all R:Base crashes. Probably 99% of the time it's a programming problem or a software issue outside of R:Base. Hope that helps. Mike Ramsour voice: 740-829-4340 -----Original Message----- From: rich Jasinski [mailto:[EMAIL PROTECTED] Sent: Thursday, July 10, 2003 7:00 AM To: [EMAIL PROTECTED] Subject: [RBASE-L] - RBw65.exe has caused an exception I have a client that has the latest version of 6.5++. They are experiencing a great increase in the number of time rbase crashes with the above error. When looking at the Dr Waqtson log it is always an access violation. The machine is a new 1.7gz with 2 gig of memory running win2000 professional. The problem seems to occur when a command file is selected off of a APP pull down. The comand file starts executes a few lines of code then crashed. When I trace the command file it runs without a problem. Any ideas? rich
