Write Conflict

[Duck]

I have a rather simple single user database that among other things
contains two forms, each with an embedded Pivot Chart that displays
sales totals, and products received totals respectively, over time,
for several vendors.

On each form I have a command button which opens the other form and
passes the particular vendor name as the OpenArgs argument so that the
different Pivot Chart information can be viewed for the same vendor.

My problem is that I keep getting the error message in an error msg.
box titled “Write Conflict”…”This record has been changed by another
user since you started editing it. If you save the record you will
overwrite changes that the other user made”

I am the only user of this database, which is just a simple .mdb file,
not accessing any type of database server.

 

[Paul Shapiro]

If you as a single user edit the same table row in 2 different forms that
are open at the same time, that constitutes a write conflict. It seems like
you're just reading data, and not updating, but maybe some fields on the
forms are being edited? Readonly access to the same row in two different
forms should not be a conflict. So look to see where you're updating data.

I have a rather simple single user database that among other things
contains two forms, each with an embedded Pivot Chart that displays
sales totals, and products received totals respectively, over time,
for several vendors.

On each form I have a command button which opens the other form and
passes the particular vendor name as the OpenArgs argument so that the
different Pivot Chart information can be viewed for the same vendor.

My problem is that I keep getting the error message in an error msg.
box titled “Write Conflict”…”This record has been changed by another
user since you started editing it. If you save the record you will
overwrite changes that the other user made”

I am the only user of this database, which is just a simple .mdb file,
not accessing any type of database server.

 

[Paul Shapiro]

You are also the other user. Each form has a separate copy of the recordset,
so each form is a "user" in the context of that error message.

You should only see this error if you are editing data, not if you're just
viewing it. If you are editing, maybe you can put both charts on the
original form. Use a tab control to share the physical form space if you're
out of screen room. If you're not editing any data, you could disable
AllowEdits on the data tab of the form properties.