>>>If your error handler simply does a return when this occurs then processing continues as before. Unfortunately, it's not simple to catch. The only thing that I know of that works in even evaluating numeric overflow is "*" $ TRANSFORM(table.field). I suppose that a field level rule could be used on the insert to blank the field in this instance.
>>
>>Here is an alternative expression:
>>
>>
>>if Table.Field = 1/0
>> ...
>>
>
>It worked prior to 7.0, but not in 7.0. The suggestion I made works in both 6.0 and 7.0.
Interesting. Well, I am still using VFP 6. Could you tell me what would happen in VFP 7? Error message "division by zero", perhaps? (Even in VFP6, $1/0 doesn't work.)
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)
