Hi If you are working in RBASE for DOS, Trace does not work in a called program if at the end of the program there are empty lines. When something like that appears, rbase goes back to no tracing. In this case I check that there is no empty lines at the end of the program nor near the end and that it ends with return. In some cases, trace jumps above some lines, with no reason. I then check all the code, rewriting it some times or modifying the logic. It sometimes work but not always.
Hope it helps. Regards. ou salutations (l'anglais nous envahit.) J.J. Laubl� ----- Original Message ----- From: "J.M. GRATIAS" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Saturday, November 08, 2003 11:50 AM Subject: [RBASE-L] - RB 4.5++ abort messages Hi everybody, A client running an old 4.5++ app is in trouble : Rbase is aborting and returns to W9x when executing a SELECT RBase debugging messages are displayed, but so fast that they can't be red. Is there a way to trace/record those messages ? I tryed : OUTPUT FileName SELECT ..... But resulting Filename is empty, because not closed properly .... Any Ideas how to trap screen display ? TIA J.M. GRATIAS, Logimatique
