T
TJ
I have a form, which contains a subform with information
on it. I have had to break the subform up into the main
subform, and different fields that are actually subforms
stored on the subform (because of the troublesome unique
table property).
In doing so I was able to code everything in correctly,
but I have run into another problem. I have a drop down
list box that once selected from updates the entire main
subform of information. This is coded in correctly, but
once I click on one of the other subforms on the main
subform I get the "Write Conflict" error:
"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 the only person in the database so this is just a
precautioninary error. I was wondering if there is a work
around for this error or anyway to turn this error off.
Thank you for your time and efforts.
T.J.
on it. I have had to break the subform up into the main
subform, and different fields that are actually subforms
stored on the subform (because of the troublesome unique
table property).
In doing so I was able to code everything in correctly,
but I have run into another problem. I have a drop down
list box that once selected from updates the entire main
subform of information. This is coded in correctly, but
once I click on one of the other subforms on the main
subform I get the "Write Conflict" error:
"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 the only person in the database so this is just a
precautioninary error. I was wondering if there is a work
around for this error or anyway to turn this error off.
Thank you for your time and efforts.
T.J.