|
I would just fake out the debugger by using the field you want to see in a statement. Like if Field1 <> field2 endif or some such hth, Dave B >>> dan27649@xxxxxxxxx 07/01/2005 1:08:46 PM >>> I searched the archives, and am probably mismembering, but... I thought there was discussion awhile back about being able to dump unreferenced fields (those which get the *RNF7031 next to their names). Via an enhancement by Hans & Barbara. We are currently on V5R2. I just spent 15 minutes scratching my cranium because I got blanks as a result of an EVAL in a debug session. (15 minutes wasted on the Friday of a holiday weekend is not a good thing.) The field was a key field in a file that was just chained to, but because it was not referenced in the program, I guess the debugger doesn't show the value. It seems to me that one of two things should happen. Either show the value, even if it isn't referenced, or show a message that states something similar to CPF7E12 ("Identifier does not exist"), maybe "Identifier exists, but is unreferenced in the program". Even though the former has appeal to me, perhaps the latter is more appropriate. At least I would keep more of my hair. TIA, Dan
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.