Subj : database access using Perl
To   : Jame Clay
From : mark lewis
Date : Mon Jul 16 2001 07:51 am

 RJ>> It's entirely possible that those are harmless
 RJ>> warnings, and not really errors.

 JC>     No, what I think it is, is that a couple of lines
 JC> in the nodelist are badly formed;   perhaps are one
 JC> field short.   In any case, a field that's expected
 JC> to have something in it, doesn't;  either nothing, or
 JC> perhaps the wrong type.

could it be that you're expecting something that isn't? the nodelist doesn't 
have a set number of fields in each record... there is a minimum, though...

1, 2,       3,           4,         5,             6,   7

 ,10,some_bbs,some_city_NC,some_sysop,1-919-774-5930,2400

is a proper listing... seven (7) required fields, the first of which may be 
empty... _lack_ of 'CM' denotes that it is not a CONTINOUS MAIL (*not* crash 
mail!) system... lack of a 'X?' flag shows no FREQs serviced... anything else 
would be modem capability and then there are userflags which may appear as

  U,FLAG1,FLAG2,FLAG3

        or

  UFLAG1,FLAG2,FLAG3

oh! and what order are you looking for things in? is it required that 'CM' (if 
it exists) come before the 'X?' FREQ flag?? and modem flags... nice tangle we 
may see there... and then there's the newer stuff for ION (internet only) and 
(what i call) fully connected systems (have both dialup and internet)... i 
suppose for truely 'fully' connected systems, there'd also be a HAM radio link 
in addition, at least...

)\/(ark

 
* Origin: (1:3634/12)

.