----------------------------This is just out of general interest although maybe of specific interest to MikeB:
I have been struggling with a pause command where I was building a multi-line message using the output from MikeB's FileUtil.DLL. I was trying to get the individual items on separate lines but the pause command would only produce one line although if I SHOWed at the R:> the vMessage variable that contained the text I got the multi-line output correctly. Eventually I saw that the length of the first line of the output from the dll (file name) was always 256 characters - even though the text that I could see was only 10-20 characters - and it dawned on me that PAUSE wouldn't produce a display that wide. Fair enough, simply remove the blanks, I thought... I tried every combination of TRIM/STRIM/LTRIM/LJS functions to get rid of what I assumed were spaces but nothing would work. The size of the variable obstinately remained at 256! And it increased further as I added each subsequent line. Oh, joy! Eventually I resorted to SGETting each character in turn and rebuilding the variable with the character only if it's ASCII value was between 32 and 255 - on the assumption that there was one or more "unprintable" characters in the string. Wonderfully, this reduced the size of the variable to the same as the visible text and my pause command then worked. The oddest thing was that the ICHAR value of the extra text appears to be zero (Null) which probably explains why the various TRIM functions did nothing. I'm sure that I don't understand how a string can contain lots of nothing but I now know how to get rid of a load of it!! Regards, Alastair ---------------------------- Alastair Burr St. Albans, UK. [EMAIL PROTECTED] -----------------------------
