Jim,
Something is out of balance... most likely a missing quote or paren. I
wonder if an embedded single/double quote in the data could cause a
problem, like O'Niel?
Ben
Jim Belisle wrote:
Razzak,
I have attempted this at least four times. Things seem to be going well
then all of a sudden this error comes up, "Error no while, switch of if
blocks are open on current input source (466)" I have no idea what
table this is referring to since the tables go by so fast and they are
not checked in any particular order. It is obvious there is a problem
somewhere. What do I do next since I have no idea of how to care for
the problem?
Jim
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of A.
Razzak Memon
Sent: Wednesday, March 12, 2008 3:04 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: 7.6 crash
At 02:57 PM 3/12/2008, Jim Belisle wrote:
We just recently purchased RBASE 7.6. I run on Windows xp
professional. In the past RBASE 6.5 has crashed especially
when manually sorting reports. I thought that problem would
go away with 7.6. Unfortunately, 7.6 is crashing more often
than 6.5 did. I have been reviewing the tutorial and trying
to update some forms in my database and 7.6 keeps locking up
and crashing. Is there a setting I need to change?
Jim,
Have you ever wondered how healthy your database really is?
Are all defined indexes properly indexed?
Are there any duplicate indexes?
Are all Primary/Foreign/Referenced keys valid?
Are all defined default column values still valid?
Are all defined views still functional?
Is there any inconsistency in performance?
These issues become important concerns when upgrading/migrating
from an old (LEGACY) DOS or Windows version of R:BASE.
Technically, there is very little to worry about when your
database is designed and managed using the latest Data Designers
(RBDefine), Enhanced CREATE and LOAD commands of R:BASE that
fully enforce all rules and validate everything before the table
is created/saved or the data is loaded. Granted, all things must
be considered.
However, if you have upgraded your legacy database and everything
seems to be working fine, do yourself and your lovely clients a
big favor! Perform one additional task to validate the integrity
of your database.
Follow the steps below and see if everything is "peachy".
01. Make a backup copy of the database.
02. Copy the entire database (.RB1-.RB4/.RX1-.RX4 files) on
your local drive in a separate folder with at least twice
as much available free disk space.
03. Start R:BASE using the latest version/update and switch the
current folder to the appropriate database folder on your
local drive.
04. At the R> prompt:
DISCONNECT
SET MESSAGES ON
SET ERROR MESSAGES ON
SET MULTI OFF
-- CONNECT the database with OWNER password, if any
CONNECT dbname IDENTIFIED BY owner password
-- CONNECT the database with no passwords
CONNECT dbname
05. Check the connected database CHARacter settings, especially
the IDQUOTES.
At the R> prompt:
CLS
SHOW CHAR
-- Notice the setting for IDQUOTES (the last item on list).
If this setting is blank/null, make sure to set the IDQUOTES
settings to ` (that is a single reversed quote, on the same
key as the ~ tilde).
SET IDQUOTES=`
06. Now create the unload file with NULL set to -0-.
At the R> prompt:
CLS
SET NULL -0-
OUTPUT newdb.ALL
UNLOAD ALL
OUTPUT SCREEN
This step will create two files (newdb.ALL and newdb.LOB)
07. DISCONNECT, and then rename this database to some other
name.
At the R> prompt:
DISCONNECT
RENAME dbname.RB? dbnameBK.RB?
08. Now, let's rebuild the fresh database and see if it passes
the integrity check.
At the R> prompt:
CLS
RUN newdb.ALL
-- Watch the activity and all messages on the screen.
-- Don't fall asleep. You might miss an important warning.
-- Completion time may vary based on size of the database
-- (number of tables/records/indexes)
If there were no warnings or error messages, you've got a
fresh/healthy database. Give yourself a pat on the back.
If there are any warning or -ERROR- message(s), take them
seriously. In that case:
-- DISCONNECT the bad database (built using RUN newdb.ALL)
At the R> prompt:
DISCONNECT
-- Delete the bad database
At the R> prompt:
DELETE dbname.rb?
DELETE newdb.ALL
DELETE newdb.LOB
-- Rename the previously saved database (Step 07.)
RENAME dbnameBK.RB? dbname.RB?
-- CONNECT to the database
CONNECT dbname
09. CORRECT all -ERROR-s accordingly and then repeat Step 06.
10. Do not quit or give up until you see a completely fresh
database without any warnings or errors.
Hope that helps!
Believe me, the time spent on this exercise will save you a
lot of hassle and embarrassment, instead of chasing something
obvious that should have been taken care of a long time ago.
Additional housekeeping and database maintenance tips are also
available on From The Edge: http://www.razzak.com/fte/
. Using Enhanced UNLOAD STRUCTURE Command in R:BASE (03/16/2007)
. Database Maintenance (R:BASE 7.6 for Windows) (05/14/2007)
Very Best R:egards,
Razzak.
