Let me play Devil's Advocate for a moment: Most things being equal, I would expect wrongly written code not to work and give an error message but not to either crash the program and/or hang/crash the PC. This is especially required when testing blocks of code - if you can't test and get a "sensible" error message then it's very hard to work out what's wrong.
What's the point of a program to check the database if it doesn't report some problems? If I take my car to the garage for a check-up I want it certified fit for all roads and all conditions - not just for dry & wide roads in summer. Networks will probably always be capable of introducing errors but by the time a database is working on a network there ought to be a fair certainty that everything is working properly. If somebody has to develop across a network then that person _probably_ knows enough about the pitfalls that a network is likely to throw up and take account of them. I removed CrashGuard this morning and since then R:Base has crashed twice - more or less par for the course. Both times I needed to re-boot my PC and I got no error messages to guide me as to why it crashed. It wasn't too hard to work out why on these occasions as I was working on a new block of code and I got the syntax wrong (see posting on using mdi forms). Both these crashes came while using TRACE which, surely, is supposed to check the syntax before it runs it. Regards, Alastair. ----- Original Message ----- From: "Sami Aaron" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Sunday, December 29, 2002 3:56 PM Subject: [RBASE-L] - Criteria For My Unstableness With R:Base6.5++ Build 1.862 > Ben - > > I have found that R:BASE for Windows is extremely stable. If there are > lots of crashes, it is caused by one of three things: (Before you begin, > put on your Sherlock Holmes hat!) > > 1. My programming code - I either define a variable with the wrong > datatype, or it was still in memory from somewhere else with the wrong > datatype, or it didn't exist when my program was expecting it to exist. > TRACE your program carefully, watching variable definitions and datatypes - > along with Javier's suggestions for checking for un-defined but referenced > variables in reports and forms. > > 2. Something is corrupted. Either the database - and if the database was > converted from an older version of R:BASE, it could have some corruption in > it that does not show up in AUTOCHK or R:SCOPE. Do an UNLOAD of structure > and data and rebuild the entire database. OR in your case, it might be the > report itself. I'd re-create the report from scratch and see if that fixes > it. > > 3. Check network/hardware issues. This doesn't seem to be an issue since > you've tried it on different systems. > > Your statement that the problem is in "the same area in programming." makes > me think even more strongly that it's a programming bug ... If you'd like, > post your block of code here and we'll see what we can make of it! > > Sami > > ----------------------------------------------------------- > Sami Aaron > Software Management Specialists > 19312 W 63rd Terr > Shawnee KS 66218 > 913-915-1971 > http://www.softwaremgmt.com > > > ----- Original Message ----- > From: Ben Strickland > To: RBASE-L Mailing List > Sent: Saturday, December 28, 2002 9:44 AM > Subject: [RBASE-L] - Criteria For My Unstableness With R:Base6.5++ Build > 1.862 > > > This is a list of when the system crashes and I have tried this very same > system on three different operating systems: > > When I go into some forms and reports even from the >R prompt. > When I use or input an extended where clause with a sort by it crashes every > single time on all three systems. > When I print a report with say 1 row of data after printing a report with 80 > rows of data it crashes on all three systems. But if I print a short report > behind a short report or vice versa it seems to be stable. > I did notice however, when I clean the database and input new data the > system seems to be more stable but still crashes at times. > I do have the same problem from the >R prompt with the above stated > instances. > R:Base has looked at this database and my code but seems to cannot duplicate > my problem. I became concern when I had three different systems to incur > the same unstableness at for the most, the same area in programming. > > I just wanted to know anyone else is experiencing this or has in the past? > Thank you. > > Benjamin Strickland >
