Guenther, Benedict, > > My guess is that a NaN somehow got into your AWL database. > > Things are much more complicated, or rather weird, than that. > > According to Benedict's reports and pasted snippets, he got an NaN score > for at least 3 rules: FROM_ILLEGAL_CHARS, AWL, MSOE_MID_WRONG_CASE
You are quite right, I wasn't paying attention. The NaN from AWL is more likely than not just a side effect of a NaN produced previously by other rules. With some luck, the patch (my first or the second) could also trigger a warning on a primary cause when it occurs, not just on AWL. Mark
