>>Yes, that's why I spent over an hour tearing hair out - I checked every which way to Sunday to verify the values but never confirmed until desperate what OLDVAL was returning .NULL.
>
>Don't really know what to suggest - just a couple of SWAGs:
>
>- is it possible your table is corrupted, or somehow actually contains a .NULL. even though it should not be possible?
>
>- has the table record pointer been at EOF() at any time?
>
>- any sort of database trigger etc. in place?
I think OLDVAL() might also return .NULL. for a new record.
Regards, Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
