Hi,
I have one application developed in MS Access as front end and SQL Server is
used as back end database. For database connectivity i have used link tables
through ODBC.
This application was working properly since one year but now facing one
problem while updating/editing some records not on all the records and i am
unable to identify for which criteria it is not validating. Below is the
message which apperars in updation of some records (Please note this message
doesn't appear for all the records, new records are being saved properly,
editing of some records creats problem)
********** Error Message Starts Below****************
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.
Coping the changes to the clipboard will let you look at the values the
other user entered, and then paste you changes back in if you decide to make
changes.
********** Error Message Ends Here *****************
*** Following options/buttons are available ***
Save Record | Copy to Clipboard | Drop Changes
Problem in this option is with "Save Record" which remains disable.
Any one who can help me in this regard.
Best Regards,
NR
Douglas J. Steele - 01 Mar 2006 11:41 GMT
Are you sure there isn't another user updating the tables? (Note that you
could, in fact, be that other user if you have two copies of the data open
in your application)

Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)
> Hi,
>
[quoted text clipped - 29 lines]
> Best Regards,
> NR
NR - 01 Mar 2006 14:11 GMT
Yes.. I am sure that time no other is updating that record.. Even i have
tried it with single instance of that application too but problem is same for
those particular records. When i make those changes directly in SQL Server
that doesn't creat any problem so SQL Server is not playing any roll in
validation failuer..
Please help in this regard.
> Are you sure there isn't another user updating the tables? (Note that you
> could, in fact, be that other user if you have two copies of the data open
[quoted text clipped - 33 lines]
> > Best Regards,
> > NR
Hal Totten - 22 Apr 2006 14:38 GMT
I have seen this when updating smalldatetime fields. Are you using Access
2003? This is the only version I have seen the problem with? If the DB is
Access 2000 format, try using Access 2000 to duplicate.
> Hi,
>
[quoted text clipped - 23 lines]
> Best Regards,
> NR
NR - 22 Apr 2006 15:53 GMT
Yeah It was developed on Access 2000 format and now is being used on both
2000 & 2003 versions..
I hope you have guessed right, problem could be with smalldateandtime fields.
As since its been long i had not got resolution so i have already shifted
back end database to MS Access.
Thanks for the help. It will really be a key point in further application.
NR
> I have seen this when updating smalldatetime fields. Are you using Access
> 2003? This is the only version I have seen the problem with? If the DB is
[quoted text clipped - 27 lines]
> > Best Regards,
> > NR