First, do you have a real name? or would you like to remain anonymous on this
Official R:BASE List Server?
Having said, that:
The upcoming in-line patch-3 for R:BASE 2000 (ver 6.5++), currently under
private beta, introduces the following three new CVAL functions to keep track
of errors:
01. (CVAL('Error Variable')) -- Title says it all.
02. (CVAL('Last Error')) Function:
This is an alternative to the current ERROR VARIABLE system of -ERROR-
trapping. Something more along the lines of an error variable which must be
EXPLICITLY CLEARED.
Why? The current system does not allow error trapping in nested code segments
or large blocks of code. Furthermore, since the -ERROR variable is automatically
cleared after each command, it requires error trapping logic immediately after each
command.
03. (CVAL('Error Detail')) Function:
When an -ERROR- occurs now you can track additional information including
the name of the file being run and the byte offset within the file. If the thing being
run is a procedure it saves information on the select used to fetch the procedure
too. We have implemented a new method of simple "stack" to keep the last three
errors. To see the information tracked use this new CVAL option.
SET VAR vError = (CVAL('Error Detail'))
Each time you call this particular CVAL function the stack pointer decrements so
successive calls allow you to see all three errors. Call it a fourth time and you will
see the first one again, etc.
If you are using R:BASE 2000 (ver 6.5++), Build:1.851xRT03 or higher and would
like to test the final beta (1.860xRT03), send your request to:
mailto:rdcc@;rbasetechnologies.com
Enjoy and make sure to have fun!
Very Best Regards,
Razzak.
At 04:54 PM 11/11/2002 -0800, rbase rbae wrote:
Greeny here.
I need directions, or suggestions to how I may find solutions as indicated below:
What's the best way to keep track of error?
Say I want to create errorlog.txt for rbase to log
all errors, this will give me a heads up on what my
error is when i get rbase error such as:
"RBG65.EXE has generated errors and will be closed by windows"
and other errors that can occur during RBG65.EXE execution.
thankx
================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
