Yes, I've had this happen too. I resolved it by reloading the database. My guess is that it is one of the system tables, possibly sys_layouts, that gets corrupted.
Regards, Alastair. ----- Original Message ----- From: "SHARON LIMA" <[EMAIL PROTECTED]> To: "Rbase List" <[EMAIL PROTECTED]> Sent: Friday, December 14, 2001 3:11 PM 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
