> I thought the reason the VAL field was only posted by the record was to give
> the record the ability to refuse a value written to it and not have anyone
> else notified that the value had been written.
That could very well have been the original reasoning, it looks like puts to the VAL field have behaved like that since the very earliest commits I have access to (1990).
I now accept that the existing behavior is correct, but it is confusing to users that DB puts to the VAL field behave differently than to every other field.
Tim Mooney wrote:
> I thought the reason the VAL field was only posted by the record was to give
> the record the ability to refuse a value written to it and not have anyone
> else notified that the value had been written.
That could very well have been the original reasoning, it looks like puts to the VAL field have behaved like that since the very earliest commits I have access to (1990).
I now accept that the existing behavior is correct, but it is confusing to users that DB puts to the VAL field behave differently than to every other field.