Marc: In my experience when I was having rashes of crashes (mostly when doing data loads and refreshes) there was usually one or two lines of less than perfect code. I stepped through each of my programs line by line and found a couple of cases where I had two continuation characters (+ +) on a command line and other cases where I had a "hanging continuation" where the command should have been complete but there was one extra "+" sign at the end of the line. Ironically the programs would crash at different points in time. There was no real consistency.
I've also had cases where I left out an "AND". R:Style does not trap for these particular errors. It's a great program and I strongly recommend that you use it if you haven't. Additionally, there may have been some conflict between versions of my antivirus software and the Adobe Acrobat Distiller. Make sure you have the latest versions of all software, patches, updates and all. I used the Distiller software to write out an R:Base report into PDF format so it was present in memory. Adobe indicated that were conflicts between it and Norton Antivirus. I downloaded some patches to correct the problem. Another evidence of problems was that my programs were running much slower than they should have. Once I corrected the above-mentioned problems my programs really started to fly. It is extremely rare to have any crashes now. I'm running 6.5++ on a Windows 2000 system. Since I have fixed these problems I now load several hundred megabytes of data on over 80 tables each morning and then run another 50 updates and reports in just a little over an hour every day. It works smooth as butter. One other thing to watch for is database size. My database was running 1.5 GB. By the time I did all my data loads I was actually exceeding the 2 GB file size limit on my 32-bit operating system. It's a wonder I didn't have more problems with my data. I have since trimmed the database down to a more manageable size, allowing for growth. I do a reload of the database each day. Hope something here helps. Mike Ramsour -----Original Message----- From: Dan Goldberg [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 15, 2004 10:05 AM To: [EMAIL PROTECTED] Subject: [RBASE-L] - RE: Crash City I would keep a log of where it crashes in the app. That should point you to the bad code. It also depends if you are you are using it with multiple users. If so, a different set of rules apply. For example, you can not modify tables when other people are in that table. I have been there and it has fustrated me. But I did find the error in my code and fixed it. Dan Goldberg -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of marc schluter Sent: Tuesday, June 15, 2004 5:59 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Crash City Hi all I have been fighting this for over 1 year and have reached the end of my rope. I am using XP pro and 6.5++ the latest build. RBase crahes about 2-3 times a day. About 3-4 times a week the data gets trashed and I need to use a backup. It is not the same place in the program that crashes. One part will crash a few times then that part to the program will work for weeks but another part will start crashing. I have installed new RAM, reinstalled XP. Trapped the last 3 errors into a table and fixed all of them many months ago. The only errors I get are putting text in a date field or something like that. What else can I check. If my code was bad I would expect it to crash in the same place each time I run that code? Or am I wrong? Marc __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail
