Access Write Lock

[Nakul]

Hi,

I am getting the following error when I update records in MSAccess

Write Conflict

This record has been changed by another user since you started editing it.
If you save the record, you will overwrite the changes the other user made.
Copying the changes to the clipboard will let you look at the values the
other user entered, and then paste your changes back in if you decide to
make changes.

[Save Record] [Copy to Clipboard] [Drop Changes] "

I am using SQL server and Linked tables

Any help would be appreciated

Thanks
Nakul

 

[Amy Vargo]

Hi,

My name is Amy Vargo. Thank you for using the Microsoft Access Newsgroups.
It sounds like you are facing the issue described in the article below with
BIT values and floating point data types.

To resolve the problem with bit data type, do one of the following:

- Using SQL Server, open the table in Design view, and assign a default
value of 0 (zero) on all bit fields. NOTE: With this option, you must
update records that were entered before this change was made. See the
next item for more information.

- Using SQL Server, run an Update Transact-SQL statement against the
table, and set all bit fields that have a value of Null to a new value
of 0 or 1.

- Using SQL Server, change the bit fields to some other data type, such
as int or tinyint.

- Using SQL Server, add a timestamp field to the table.

- Use a Microsoft Access project (*.adp) instead of an Access database
(*.mdb).



To resolve the problem with floating point data types, do one of the
following:

- Add a timestamp column to the SQL table. (JET will then use only this
field to see if the record has been updated.)
- Modify the data type that is in SQL Server to a non-floating point
data type (for example, Decimal).
- Run an Update Query to update the record. You must do this instead of
relying on the recordset update.


For more information, see the article below.

280730 ACC2000: Write Conflict Error When You Try to Update Records in a
Linked
http://support.microsoft.com/?id=280730

I hope this helps! If you have additional questions on this topic, please
respond back to this posting.


Regards,

Amy Vargo
Microsoft Access Engineer


This posting is provided 'AS IS' with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

 

[Alp Bekisoglu]

Mis Vargo,

I know it is not proper to insert a question within another but since you
mentioned "timestamp" and I have been trying to find it out, I'm kind of
forced to do the improper if the group wouldn't mind:
Is there the same facility in Access 2000/2002 (mdb)?
- I'm refering to the numeric string that bases on a value since 1/1/70, or
something similar

Apologies once again, and thanks in advance.

Alp

 

[Douglas J. Steele]

What exactly are you looking for, Alp? Is there what "same facility" in
Access 2000/2002? Are you trying to get an indication of when a row was
inserted? Create a date field, and set its default value to Now().

For what it's worth, dates in Access are stored as 8 byte floating point
numbers, where the integer part represents the date as the number of days
relative to 30 Dec, 1899, and the decimal part represents the time as a
fraction of a day. If you need to convert an Access date to the Unix-style
date (number of seconds since 1 Jan, 1970), you can use DateDiff("s",
AccessDateValue, #1/1/1970#) and you can convert back using DateAdd("s",
UnixDateValue, #1/1/1970#)