Thanks Eric I did do that search and found no other
"error" word except the one at the end where is reported
"Errors have been encountered."

"Eric M. Bienstock, Ph.D." wrote:
> 
> | I have scanned the report several times and have found nothing amiss.
> | Am I going blind?
> ---------------------------------
> 
> Sharon,
> 
> Don't depend on your eyes.  Load the error report into a text editor and do
> a search on the word ERROR.  It's easy to miss in an AUTOCHK report
> containing lots of tables/views.
> 
> ---------------------------------------------------------------------------
> Eric M. Bienstock, Ph.D.
>    Database Development, etc.
>       Authorized R:BASE Developer
>          Eric M. Bienstock & Associates, Inc.
>             day: 212-978-7948    eve:  973-763-8650(8)
>                FAX:  209-882-9250    [EMAIL PROTECTED]
>                    http://members.home.net/ericmb/Ericmb.htm
> ---------------------------------------------------------------------------
> 
> ----- Original Message -----
> From: "SHARON LIMA" <[EMAIL PROTECTED]>
> To: "Rbase List" <[EMAIL PROTECTED]>
> Sent: Friday, December 14, 2001 10:11 AM
> Subject: Autochk Error Messages
> 
> | Hi All,
> |
> | Off site location - Runtime 6.5 +
> |
> | I have captured the AUTOCHK FULL report into a file.
> | There is a message at the end:  ERRORS HAVE BEEN ENCOUNTERED.
> | With this message at the end there are usually details about
> | the problem area.  However, on this report there are NO DETAILS.
> | I have scanned the report several times and have found nothing amiss.
> | Am I going blind?
> |
> | I did set an error variable which returned the number 1243.
> | That error number is not in the list I have available.
> | Where can I get a new list of error identification numbers?
> |
> | Does someone have experience with this?
> |
> | Thanks,
> | Sharon
> |
> | ================================================
> | 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 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 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

Reply via email to