I have a client who experience a break out to the debugger with RTP11 (which is READNEXT) with the message that the "Break key was hit". As it turned out one of their files was somehow corrupted in that the data was in the file but it was not accessing the keys. So for example if you did a LIST FILENAME, it would say zero records.

My question is: does the Revelation source for items like RTP11 have these imbedded debuggers? And if so which programs have such behavior and is there a listing of the meaning of the break-out.

Oh, by the way, and I don't think it is important to my question, the application was in RevG.

Tom Savell

What RTI did in AREV was to implement a generic Error Handler that executes a DEBUG instruction on some critical errors. Reading a Null key is one of those. Another is the bug discovered some time ago by Steve Smith (posted on his Web Site in the top 10 Bug list or some such). This drove me crazy until I saw it there. Another one that will get you is when you do an OCONV on a large multi-valued string of things and you get a Variable Exceeds Maximum Length error on @ANS. There are others as well. I'll leave it up to you to discover all the rest since my fingers are tired.

Don Miller

C3 Inc.

Boy, you old guys need to wear thimbels when you type.

;) Thanks Tom

View this thread on the forum...