>Are you using regular textbox and column (no custom classes)?

Thanks, this got me thinking. I tried hacking classes and yes it was because of the numeric textbox class I was using since 2005. I have now replaced the class with a mix from 2 classes from the UT downloads and the problem seems to have resolved.

This raises questions in my mind. If no code pertaining to the class I just replaced was executing in the coverage log then why would this problem have happened?

Just for interest purposes, after I switched to the new class those two particular values that were being truncated (36.41 and 200.79) were still dirtying the RV buffer when pressed enter on. So something was not correctly saved somewhere in the data too using the old class. As soon as I saved the, now consistent value, the dirtying behavior also went away. Not sure what happened.

Thanks