> > Yeah, the logic is the same but the usage differs a bit.  What I see from
 > > reading about, is we can generally figure out one another and ajust althou
 > > nested selects can get a little hairy.
 > 
 >     Besides any separate test databases I might create (and I'm sure I've se
 > reference to scripts for creating such things...), I'm thinking of adding
 > another table to the nodelist database I'm already working with.  Specifical
 > one for DNS related info.  Have the zone/net/node/point fields in that table
 > well, and can then do joins on that.  One thing I would take into account is
 > that there could be multiple entries for a particular node in the DNS relate
 > table...   (A & AAAA, for instance, not that IPv6 is being used
much yet...)

Definately 1 tables needed to handle it at minimum. Pkey will be the issue to
make it easier so you'd add to a full nodenumber (4d likely bet).  Add a
possible populated 5d {at}netname to the initial set and you have a generatable
key set with the + that covers more than fidonet.  substrib(15,4) sounds
right to hndle the INA but you'd need to NVL or coalesce for null values?

Just catching up with messages.  We've been busy with our new rescue pup. 
Mabel Anne.

http://www.beaglestotherescue.org/mabelanne.cfm

She came home with us last Saturday and it getting along well with all here.
      xcarol
--- SBBSecho 2.11-Win32