Hi Albert, I seem to remember a problem with OUTPUT a while back, maybe a year or more, which I reported to the list, at least.
I don't remember precisely what the problem was or the outcome but to get around it I added APPEND to the command which _seemed_ to resolve the problem. I do remember getting empty output files so maybe the problem has re-appeared? Regards, Alastair. ----- Original Message ----- From: "Albert Berry" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[email protected]> Sent: Saturday, September 24, 2005 12:10 AM Subject: [RBG7-L] - Log Files > Using the latest and greatest 7.1 for Windows build 7.1.81.30922, I have just > discovered what I consider a quirk. An automated reload routine sets the > output with the following command. The screen is included so that users know > something is going on, and when it is done, they can review the results. > > SET MESSAGES ON > SET ERROR MESSAGES ON > OUTPUT xReload.log WITH SCREEN > > and at the end of the file > > OUTPUT SCREEN > RBEDIT xReload.log > RETURN > > Here's the quirk: If I issue the OUTPUT command before connecting to the > database, the file has only 1 byte in it. If I issue it after the database > has been connected, the log file contains all the message data I expect to > see. The file will not trap the messages on a failed disconnect, which is a > bit important. > > Can anyone else verify this? Did I just notice this after all these many > years? Am I crazy? (Well, Yes, but ...) > > > Albert Berry > Management Consultant > RR2 - 1252 Ponderosa Drive > Sparwood BC, V0B 2G2 > Canada > (250) 425-5806 > (250) 425-7259 > (708) 575-3952 (fax) > [EMAIL PROTECTED] >
