Bob,   
       
   BS> fwiw, I can trigger the error anytime I want on Janis' system by   
   BS> flagging any node down.  It's happened in the past when net 140, net 342,   
   BS> and this time when net 153 flagged a node down.  Removing the "down"   
   BS> keyword, or totally deleting the node seems to solve the problem.   
       
   How 'bout deleting the whole zone? Now "that" would solve a problem ... :-)   
       
    \%/@rd   
       
       
       
       
       
       
       
       
       
       
       
       
       
   [My appologies, no insult meant. It was just too funny a thought not to write   
   it down]    
      
   --- D'Bridge 3.59   
    * Origin: Many Glacier / Protect - Preserve - Conserve (2:292/854)