I had a college proffessor that could communicate in 7 different languages, from scandanavian, to Indian, to french, to vietnamese, etc. I was very envious cause I thought I could only communicate in one language, i.e., american english. Then my wife reminded me that I can communicate in two languages. UH? American English and Southern Redneck! ju-eat-yet? no-ju?

I am assumming you are talking about a console program that runs from a command window? If so the open a second command window. In the first command window,start the program and pipe output to a text file, and in the other command window do a type command on the text file with a more option pipe. As the file fills up you can scan it at your own reading pace.

I got started when I was 20 in the service, didn't have Personal Computers back then. Only mainframes. Carc punches and readers, and tape. Using CoBOL and FORTRAN. Still making a pretty good living at coding. However, I can say I have put more than 20 applications into production, i.e., out the developer door where the "owner/client" could sell it to someone for usage and make a profit. I found that a lot of younger coders now-a-days are smart, got their certificates, etc. and they know their subject matter, but it seems like that once they have identified the saddle, bridal, and horse, they don't know how it all goes together so they can ride the horse, so to speak. I guess and more important question is how many actual out the door to be sold applications have you done and are you still doing it?

My, my... I work from home...no music, no TV, no interruptions, no sounds except the chair squeeking as I move closer and closer to my finished code....and of, course the ability to shout out a few nice words at which ever code language I happened to be contracted to code in and how it is inept at performing even some of the simplest object calls... Outside of that, I love to listen to the SWOOSH of the shaft, followed by the SMACK of the golf ball going down the fairway, and of course the eventuall ploppety plop of the ball going in the hole. Fla_Golfr, curtis.

WOW! Ya'll make me feel inept at 55 to 60 hours a week, which does not include Wednesday afternoons playing golf after lunch and Saturday mornings , and playing around with my woodworking shop on weekends making my wife wood funiture, plus yard maintenance (mowing, pool, landscaping) and having supper ready for the wife and kids, except Wednesdays of course. Of course the wife who works about the same, does fill in with taking care of the kids extra activities, like dance and gymnastics... However, her and I do plan our time together, important you know. 90 hours...did that before I wanted fullfilling life. fla_golfr... Curtis Colee No titles, just a BS in EE and 33 plus years in the IS field doing every job imaginable successfully.