Timestamp Field For Replication - Should It Have A Default Value Defined?

[Res]

I have added a timestamp field to my tables to ensure that replication will
be fully supported.

I am using Access (XP) and it does not seem to display anything when this
type of field is added to a form. Is this correct and should I define a
default value for any timestamp fields in table design even though Access
does not appear to display the contents?

TIA

 

[Steve Jorgensen]

I have added a timestamp field to my tables to ensure that replication will
be fully supported.

I am using Access (XP) and it does not seem to display anything when this
type of field is added to a form. Is this correct and should I define a
default value for any timestamp fields in table design even though Access
does not appear to display the contents?

TIA

Because timestamp fields hold raw binary data, Access will not display their
values on datasheets or bount controls. To see that there really is data in a
TIMESTAMP field, open a recordset from code, copy the value of the field to a
variable dimensioned as <var>() As Byte, then loop though the elements of the
array, and print each value.

 

[val]

I have added a timestamp field to my tables to ensure that replication will
be fully supported.

I am using Access (XP) and it does not seem to display anything when this
type of field is added to a form. Is this correct and should I define a
default value for any timestamp fields in table design even though Access
does not appear to display the contents?

TIA