Good to hear that. "Check" to me was always a rather odd thing to find in a protocol specification. But I implemented it as instructed. I don't remember if it ever caught any bugs in the code I worked on, but it did seem to be a useful set of consistency checks so I didn't complain about it. paul On Aug 25, 2012, at 7:13 PM, Rob Jarratt wrote: I found a bug in my adjacency processing that made other adjacencies use index 0 in the decision database, I think that is what has been causing the Check failures.