Access 97 SQL Server 2005- Write Conflicit

I am getting the write conflicit when 2 users access the same record
the first one to save is allowed but the second user gets the message
Write conflicit with the save option greyed out.

I have seen this error on many forums and implemented the following

See the default for int to 0
Added a field with type timestamp
Updated all the records to ensure all fields contained valid records

But i am still getting the error.

Although i have added the timestamp field it is blank , my application
does not update this field and i dont know ehere it should get the
timestamp data.

Any help please - much appreciated

Regards

Pat

pnjones@gmail.com wrote:

Quote:

I am getting the write conflicit when 2 users access the same record
the first one to save is allowed but the second user gets the message
Write conflicit with the save option greyed out.
>
I have seen this error on many forums and implemented the following
>
See the default for int to 0
Added a field with type timestamp
Updated all the records to ensure all fields contained valid records
>
But i am still getting the error.
>
Although i have added the timestamp field it is blank , my application
does not update this field and i dont know ehere it should get the
timestamp data.
>
Any help please - much appreciated
>
Regards
>
Pat
>

Open up the table that contains the TimeStamp field. YOu could enter
Now() as the Default Value. When a record is first created the value
will be the time it was created.

You could, in the BeforeUpdate event of the form where the records are
added, entere something like
If Me.NewRecord Then Me.DateStampFieldName = Now()

Write conflicts between Access and Sql Server are a known issue. There
are a few workarounds like using the timestamp datatype - note: in sql
server this datatype is a binary datatype - it has nothing to do with
Now() or dates. It is kind of like an autonum column - a unique
identifier. The other thing you could do is to not allow nulls in any
of the varchar columns - make them default to '' (zero length string).

The real fix is to use .Net applications when interfacing with Sql
Server. The .Net dataAdapter compensates for concurrency issues very
well, and I have not encountered any write conflicts with sql Server
using .Net tables.

Rich

*** Sent via Developersdex http://www.developersdex.com ***

On Fri, 17 Nov 2006 13:22:39 GMT, salad <oil@vinegar.comwrote:

That is a common misconception. From BOL:
Timestamp Is a data type that exposes automatically generated, unique
binary numbers within a database. timestamp is generally used as a
mechanism for version-stamping table rows. The storage size is 8
bytes.

-Tom.

Quote:

>pnjones@gmail.com wrote:
>

Quote:

>I am getting the write conflicit when 2 users access the same record
>the first one to save is allowed but the second user gets the message
>Write conflicit with the save option greyed out.
>>
>I have seen this error on many forums and implemented the following
>>
>See the default for int to 0
>Added a field with type timestamp
>Updated all the records to ensure all fields contained valid records
>>
>But i am still getting the error.
>>
>Although i have added the timestamp field it is blank , my application
>does not update this field and i dont know ehere it should get the
>timestamp data.
>>
>Any help please - much appreciated
>>
>Regards
>>
>Pat
>>

>Open up the table that contains the TimeStamp field. YOu could enter
>Now() as the Default Value. When a record is first created the value
>will be the time it was created.
>
>You could, in the BeforeUpdate event of the form where the records are
>added, entere something like
> If Me.NewRecord Then Me.DateStampFieldName = Now()

Tom van Stiphout wrote:

Quote:

On Fri, 17 Nov 2006 13:22:39 GMT, salad <oil@vinegar.comwrote:
>
That is a common misconception. From BOL:
Timestamp Is a data type that exposes automatically generated, unique
binary numbers within a database. timestamp is generally used as a
mechanism for version-stamping table rows. The storage size is 8
bytes.

I was thinking of a DateTime field in Access. Is there a TimeStamp data
type in Access besides a DateTime field?

Quote:

>
-Tom.
>
>
>
>

Quote:

>>pnjones@gmail.com wrote:
>>
>>

Quote:

>>>I am getting the write conflicit when 2 users access the same record
>>>the first one to save is allowed but the second user gets the message
>>>Write conflicit with the save option greyed out.
>>>
>>>I have seen this error on many forums and implemented the following
>>>
>>>See the default for int to 0
>>>Added a field with type timestamp
>>>Updated all the records to ensure all fields contained valid records
>>>
>>>But i am still getting the error.
>>>
>>>Although i have added the timestamp field it is blank , my application
>>>does not update this field and i dont know ehere it should get the
>>>timestamp data.
>>>
>>>Any help please - much appreciated
>>>
>>>Regards
>>>
>>>Pat
>>>

>>
>>Open up the table that contains the TimeStamp field. YOu could enter
>>Now() as the Default Value. When a record is first created the value
>>will be the time it was created.
>>
>>You could, in the BeforeUpdate event of the form where the records are
>>added, entere something like
>> If Me.NewRecord Then Me.DateStampFieldName = Now()

>
>

pnjones@gmail.com wrote:

Quote:

I am getting the write conflicit when 2 users access the same record
the first one to save is allowed but the second user gets the message
Write conflicit with the save option greyed out.
>
I have seen this error on many forums and implemented the following
>
See the default for int to 0
Added a field with type timestamp
Updated all the records to ensure all fields contained valid records
>
But i am still getting the error.
>
Although i have added the timestamp field it is blank , my application
does not update this field and i dont know ehere it should get the
timestamp data.
>
Any help please - much appreciated
>
Regards
>
Pat

Are you using forms?

What is the RecordSetType Property?
What is the RecordLocks Property?

(I don't really know if such properties exist in AC 97 forms, but
surely there is something similar if not).

Access 97 SQL Server 2005- Write Conflicit

re: Access 97 SQL Server 2005- Write Conflicit

re: Access 97 SQL Server 2005- Write Conflicit

re: Access 97 SQL Server 2005- Write Conflicit

re: Access 97 SQL Server 2005- Write Conflicit

re: Access 97 SQL Server 2005- Write Conflicit

/bytes/development

/bytes/it

/bytes/about