dave1005
asked on
Write Conflict error in Access 2010 runtime but not in full version
My database works fine on my computer (with full version of Access 2010). It doesn't on another computer (with Access 2010 runtime). I get a write conflict on that one. I click on a checkbox that is in a continuous subform. It dumps the associated record into another continuous subform for "selected" items. Clicking the checkbox in the "selected" subform removes it from that subform and puts it back into the original subform. It works perfectly with the full version of Access but not the runtime version. When I click on the checkbox I get the 'Write Conflict' error. Why? How can this be fixed?
Here is the code:
This is for a shipping tag program.
Selects the pallet and part tag numbers on it and puts it in "selected" subform(s):
DoCmd.SetWarnings (Off)
DoCmd.OpenQuery "UpdatePLoadTrk1 in Tag Entry1 to Yes"
Requery
Me.Parent![Pallets To Take Off Truck Test1 subform].Form.Requery
Me.Parent![PalletTagsNotOn Truck subform].Requery
Me.Parent![Tags On Truck].Requery
Unselects the pallet and part tag numbers on it and puts it back in "unselected" subform(s):
DoCmd.SetWarnings (Off)
DoCmd.OpenQuery "UpdatePLoadTrk1 in Tag Entry1 to No"
Requery
Me.Parent![Pallets To Put On Truck Test1 subform].Form.Requery
Me.Parent![PalletTagsOnTru ck subform].Requery
Me.Parent![Tags On Truck].Requery
Here is the code:
This is for a shipping tag program.
Selects the pallet and part tag numbers on it and puts it in "selected" subform(s):
DoCmd.SetWarnings (Off)
DoCmd.OpenQuery "UpdatePLoadTrk1 in Tag Entry1 to Yes"
Requery
Me.Parent![Pallets To Take Off Truck Test1 subform].Form.Requery
Me.Parent![PalletTagsNotOn
Me.Parent![Tags On Truck].Requery
Unselects the pallet and part tag numbers on it and puts it back in "unselected" subform(s):
DoCmd.SetWarnings (Off)
DoCmd.OpenQuery "UpdatePLoadTrk1 in Tag Entry1 to No"
Requery
Me.Parent![Pallets To Put On Truck Test1 subform].Form.Requery
Me.Parent![PalletTagsOnTru
Me.Parent![Tags On Truck].Requery
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Not a problem. You'll often find these kinds of errors when you move to a slower/faster machine. In this case, it was the difference between the runtime and the full version, but that's not really what the issue was.
The "runtime" and full version are actually one in the same, it's just a matter of registry keys that decides if you get design features or not.
The other way to fix this would be to leave the check box un-bound, but because your in a continuous subform, you needed to leave it bound so it works for all the rows.
Bit of a rock and a hard place in that regard<g>
Jim.
The "runtime" and full version are actually one in the same, it's just a matter of registry keys that decides if you get design features or not.
The other way to fix this would be to leave the check box un-bound, but because your in a continuous subform, you needed to leave it bound so it works for all the rows.
Bit of a rock and a hard place in that regard<g>
Jim.
ASKER