No need for apologies. It was just my half completed programming habit! If I had actually compared it to a small percentage the code would have made sense instead of looking very Rube-Goldberg as you pointed out. As it was just a throwaway test harness, I didn't go back and fix it.
In a test for looking at what the range of epsilon should be, I found it to be zero as you point out. There is the "practical" catching up with the "theoretical"! Tom W. has sent me an email assuring me that this problem does not occur in code for the other devices handled by DAQmxBase which is great.
(LIthium keeps adding too many Re: Re: Re: to messages...)