Carol,

> The problem with SQL is that folks do not list in the same order and
> SQL is very 'driven' by that.

   Which is why I consider, for instance, doing a query for data and using that
data as separate issues.  Not sure, though, how useful the order info in a
nodelist is...  (Although that does remind me that I don't think that nodes
underneath a hub is being properly reflected in the database, with the
ftndbpl-nodelist script as it is now...)


> The primary part is in order, but once you get after the 'phone field'
> all bets are off.

   I think, rather, the baud rate field;  but yes that can be an issue.  It's
why I think I'd try processing the flag field into a hash (associative
array) and then get the more specific info being looked for.  Just use an
SQL query to get a set of records for a particular flag, like IBN, then do
the rest of the processing from there.  
   
    

> BTW, the battlenet nodelist is pretty small and makes a decent testing
> ground.  Not but about 25 nodes in there if you want a sample one to use.
> Email or netmail me for a copy. email is cshenk1{at}cox.net

     Well, I wouldn't mind having it also;  particularly if it's one you're
using.   (Not as easy to compare what we're doing if we're not using the same
dataset...)  






Jame
jame{at}rocasa.us
rjclay{at}gmail.com


--- BBBS/LiI v4.01 Flag