[AccessD] Weird problem

Tina,

All I did was create a field which I called TimeStamp and make it a data type timestamp.  AFAIK you 
can call the field anything you want but calling it TimeStamp seemed useful to me.

If I go into my table and view data, that field just shows 'binary', i.e. you cannot see the actual 
value at least doing it the way I am doing it.

I did not have to go backfill or anything.  And my problem with that one record was instantly gone. 
  I went back to my access app, relinked and tried to edit the problem record, in the table and in 
the form, and there was no problem any more.

As everybody says, it is not actually a time stamp and it is not in fact even a date / time data 
type, it is binary apparently.  AFAICT the sole purpose is to allow clients to get the "timestamp" 
when they are trying to modify the record.  When it is time to actually do the save they can compare 
the "timestamp" they got against what is currently in the record and if they are different then the 
record has been modified since they pulled the data.

According to this:

http://msdn.microsoft.com/en-us/library/ms182776.aspx

Timestamp is being deprecated in favor of RowVersion however in my version of SQL Server RowVersion 
is not a data type whereas timestamp is.

I dunno...

John W. Colby
Colby Consulting

Reality is what refuses to go away
when you do not believe in it

On 1/11/2012 8:48 AM, Jim Dettman wrote:
> Tina,
>
>    It's just a data type in SQL.  You do nothing with the field other then
> add it to the table.
>
> There are a couple of MSKB articles that fill in the detail:
>
> Optimizing Microsoft Office Access Applications Linked to SQL Server
> http://msdn.microsoft.com/en-us/library/bb188204(v=SQL.90).aspx
>
> Look in the section "Understanding and Addressing Updatability Issues" and
> then "Supporting Concurrency Checks" within that.
>
> This one goes a little bit into the keyset model that JET uses to maintain
> record sets and why issues arise with ODBC data sources:
>
> PRB: Explaining "Record is deleted" error accessing ODBC table
> http://support.microsoft.com/kb/172339
>
> Jim.
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Tina Norris
> Fields
> Sent: Wednesday, January 11, 2012 07:59 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Weird problem
>
> Jumping in here, not because I have much to offer, but because I have
> much to learn.  Please discuss the time stamp field.  How should one be
> made?  How should one be used?  Thank you for sharing your knowledge.
> T
>
> Tina Norris Fields
> tinanfields at torchlake.com
> 231-322-2787