Why and I getting this error message, "This record has been changed by another user since you starte

[Kelvin Beaton]

I get the following error message when I try to edit a value in the query.
It actually give the same error if I try and change it in the table also.

"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.

Copy the changes to the clipboard will let you look at the values the other
user entered, and the pass your changes back in if you decide to make
changes."

My options are "Copy to Clipboard" or "Drop Changes"

I have a GetDate() as the default value for "ExceptionTimeStamp" field and I
also have a field that does basically the same thing called
"ExceptionDateRevised"

They both have the defaul value of "GetDate()" but the user can change the
"ExceptionDateRevised" value.

My gut says there's an issues with the two GetDate() defaults... Do I need
to remove on?
I tried removing one GetDate statement, but it seems to have the same
issue...

This is my query:
SELECT tbl_Families.FID, StrConv([Last]+", "+[First],3) AS LastFirstName,
tbl_ExceptionToPolicy.*
FROM (tbl_CaseNotes INNER JOIN tbl_Families ON tbl_CaseNotes.FID =
tbl_Families.FID) INNER JOIN tbl_ExceptionToPolicy ON tbl_CaseNotes.NoteID =
tbl_ExceptionToPolicy.CaseNotesID;

Access 2003 front end
MS SQL Server backend

I backed up and restored the database to a TEST db.
I'm the only one user the TEST db so there is no other user...

Any help would be much appreciated

Kelvin

 

[Jeff Boyce]

Do a search of the Microsoft Knowledge Based for SQL-Server and Timestamp.

Under certain conditions, you will need to have a SQL-Server "Timestamp"
data field in each of your SQL-Server tables. NOTE: This data type is NOT
a date/time datatype.

I was running into the same "... by another user" error and, by adding a
Timestamp field in the SQL-Server database, and refreshing my link to the
table, was able to eliminate the problem.

(with thanks to Armen Stein for the lead!)

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Kelvin Beaton]

thanks I'll take a look...

Kelvin

Do a search of the Microsoft Knowledge Based for SQL-Server and Timestamp.

Under certain conditions, you will need to have a SQL-Server "Timestamp"
data field in each of your SQL-Server tables. NOTE: This data type is
NOT a date/time datatype.

I was running into the same "... by another user" error and, by adding a
Timestamp field in the SQL-Server database, and refreshing my link to the
table, was able to eliminate the problem.

(with thanks to Armen Stein for the lead!)

Regards

Jeff Boyce
Microsoft Office/Access MVP

I get the following error message when I try to edit a value in the query.
It actually give the same error if I try and change it in the table also.

"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.

Copy the changes to the clipboard will let you look at the values the
other user entered, and the pass your changes back in if you decide to
make changes."

My options are "Copy to Clipboard" or "Drop Changes"

I have a GetDate() as the default value for "ExceptionTimeStamp" field
and I also have a field that does basically the same thing called
"ExceptionDateRevised"

They both have the defaul value of "GetDate()" but the user can change
the "ExceptionDateRevised" value.

My gut says there's an issues with the two GetDate() defaults... Do I
need to remove on?
I tried removing one GetDate statement, but it seems to have the same
issue...

This is my query:
SELECT tbl_Families.FID, StrConv([Last]+", "+[First],3) AS LastFirstName,
tbl_ExceptionToPolicy.*
FROM (tbl_CaseNotes INNER JOIN tbl_Families ON tbl_CaseNotes.FID =
tbl_Families.FID) INNER JOIN tbl_ExceptionToPolicy ON
tbl_CaseNotes.NoteID = tbl_ExceptionToPolicy.CaseNotesID;

Access 2003 front end
MS SQL Server backend

I backed up and restored the database to a TEST db.
I'm the only one user the TEST db so there is no other user...

Any help would be much appreciated

Kelvin

 

[Van T. Dinh]

Like Jeff, I recommend a TimeStamp Field for each Table in the (SQL Server)
database if you use Access as the Front-End to the database. In fact, every
Table in my SQL Server databases always has 4 Fields at the end:

CreatedBy
DateCreated
DateUpdated
Upsize_ts (TimeStamp)

(I started with an upsized JET database wihch use "Upsize_ts" as the Field
name and I just keeping using this name regardless whether the database is
upsized from JET or a new database from scratch on SQL Server).