Hi Doug,

>>>I find that when I have a View with a DefaultValue, I have to issue a SETFLDSTATE(, 4) in order for the DefaultValue to flow to my table when I TABLEUPDATE().
>>
>>You seem to be right on this. (Maybe a bug?)
>>
>One thing I thought about is that maybe a DefaultValue shouldn't be registering as a modified field since the user or program didn't really modify the record. In other words, a DefaultValue is just that, a default value. If you don't put in a DefaultValue for a logical, it's default value will be .F.. If you don't put in a DefaultValue for a numerical, it's default value will be 0 etc. This leads me to think that this behavior is by design.
>

Then default values for tables with buffer mode wouldn't be
saved as well. IAC, your right saying that it's a "feature by design"
that's the way MS ppl call to inconsistent behavior IMO! :)

BYE,

J. Luis

J. Luis Santiago Rodríguez.• CADIS • E-mail: jlsantiago@iserve.net.mx• Ciudad de México.