Stuart McLachlan
stuart at lexacorp.com.pg
Sat Aug 23 05:31:23 CDT 2014
There are at least two external uses for the SQL Server TIMESTAMP/ROWVERSION.that I can think of: 1. Requery it before saving updates to see whether the record has been changed by another user. 2. Since it is a sequential value, you can query how many/what other records have been updated since any specific record was last updated. -- Stuart On 23 Aug 2014 at 9:39, Gustav Brock wrote: > Hi Bill > > You can say that with an Access backend, a timestamp has to be > produced by the frontend, while with a server backend like SQL Server, > a timestamp is normally produced by the backend engine. However, the > nature of those timestamps may be very different. For SQL Server, a > timestamp is not readable as a time, it's for internal use only. >