If I understand what it is you are trying to say ( and that isnt
easy), then "error 7878 The data has been changed. "

means someone has changed the record in a form before someone has had
a chance to save their copy.
eg
1) Operator A opens a form at 9:18 - the customer address says "23
smith st"
2) Operator B open the same form at 9:18:30 - the customer address
says "23 smith st"
3) Operator B changes the address to "23/a smith st", and exits the
form at 9:18:45, saving their change.

4)Operator A changes the form at 9:19 - changes the address to "23-a
smith st",
The message "error 7878 The data has been changed" appears to operator
A

Congratulations - You have experienced "Optimistic Locking"

The danger is if Operator B ALSO changed the customers telephone
number, but operator A didnt, because if Operator A does save the
customer record, then Operator B's changes will be overwritten.

The solution is - Never use BOUND controls on an Access Form in an ADP

If this isnt your problem, you need to explain it better to get some
more suggestions

Accessed <rwatson (AT) westnet (DOT) com.au> wrote:

Then why use Access if you can't use bound controls? That is Access's main
advantage.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Niranjan <nhiras (AT) gmail (DOT) com> wrote:

Just post the line of code on which the errors are occurring.

Also do you have a timestamp aka rowversion field specified on each table as well as
a primary key?

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

"Accessed" makes the assumption that in "migrating to SQL Server", you
created an ADP (Access Project), which is not necessarily the case. You
might still be using an MDB linking to the SQL Server tables via ODBC. In
either case, "Accessed" is in error: Bound Forms work just-fine-thankee in
both ADP and MDB.

Optimistic locking usually works very well, indeed, also... there certainly
was insufficient information for a definitive answer, in any case. Unless
you jump through some, perhaps flaming, hoops to create a bad example, it is
rather rare for two users to be editing the same record in most business
applications.

It is extremely difficult, at best, to debug remotely. Unless the person
trying to help you is clairvoyant, it is impossible without details of what
you are doing, and that would mean, yes, you need to copy some code... not a
lot, but the code that is giving you the error.

Larry Linson
Microsoft Office Access MVP


"Niranjan" <nhiras (AT) gmail (DOT) com> wrote