Hi! Richard,

On 31 Jan 10 19:43, you wrote to me:

 RW>> Maybe, but what happens to ifnumber I wonder if the bonehead that

[ ...trimmed... ]

 RW> Yup, we figured out how it chokes.  Returns errorlevel 255,
 RW> which means syntax fubar.  So, if a bonehead types in a non
 RW> numeric command line parm ifnumber's going to give us some
 RW> argument about bad syntax.  Can use that.

Man, I could have told you that.  In fact I did mean to, though it is in
the dox for ifnumber.  The way I used it in range testing I wasn't
interested in if's, but's or maybe's, or shades of grey/gray.  Where
anything in the range proves okay then the errorlevel is zero (0); anything
else is errorlevel 1 or greater (like the 255) and is an actual error.  Oh
well.

 RW> Was working on another batch project, my vessels
 RW> reconciliation file we talked about in this echo, cleaning
 RW> up the reports it generates and was testing some code I
 RW> intended to use for it, and in so doing crash tested what I
 RW> wanted to crash test for this project as well.

This is good.  Yes, I like to hear stories like this.  At least someone
else is still doing BATch stuff.  Sometimes I get an itch to do a reality
check when I'm doing the stuff I do here.  :)  No one else sees it...
luckily.

I did have a 'win' with my ISP last week after I found out that our
homepage hadn't been working for over a year, and had them fix the glitch. 
(It's mentioned in the NLSS.bat dox.)

 RW> THe other code was critical, as it runs in automation while
 RW> I"m in bed or absent, so it's important to get right the
 RW> first time .

Cool.

Cheers,
Paul.

... Me erur corectyng modim is malphunctinyng...
--- GoldED+/W32 1.1.5-31012