Isaac
Lifelong Learner
- Local time
- Today, 04:52
- Joined
- Mar 14, 2017
- Messages
- 8,738
I have some CurrentDb.Execute.............dbFailonError statements throughout my database. They are things I run administratively, not by end users nor part of any deployed database/system.
They update sharepoint list fields. Occasionally, when the sharepoint list is busy, I'll get "cannot update - database or object is read only". I think that the root cause of this is that I am trying to update fields that the Infopath/sharepoint form is also trying to update, or something close to that along those lines.
In these cases, I assume that Microsoft Access is most likely able to update a number of records........Perhaps a few hundred out of the total = 1000 expected.
Let's say I am OK with that - I'd like Access to update whatever it can, and "skip over" the ones that it failed on, OR, (at worst), I'd like it to update whatever it can, and fail at the point when it gets to the one it can't update........But go ahead and commit any updates done up to then.
Would this be an appropriate time to leave off dbFailonError?
If so, what if I still want to KNOW that the failure happened, would Access still be expected to tell me? Would I need to use a currentdb-set variable and then check recordsaffected vs. records expected - would that be the only way to know?
They update sharepoint list fields. Occasionally, when the sharepoint list is busy, I'll get "cannot update - database or object is read only". I think that the root cause of this is that I am trying to update fields that the Infopath/sharepoint form is also trying to update, or something close to that along those lines.
In these cases, I assume that Microsoft Access is most likely able to update a number of records........Perhaps a few hundred out of the total = 1000 expected.
Let's say I am OK with that - I'd like Access to update whatever it can, and "skip over" the ones that it failed on, OR, (at worst), I'd like it to update whatever it can, and fail at the point when it gets to the one it can't update........But go ahead and commit any updates done up to then.
Would this be an appropriate time to leave off dbFailonError?
If so, what if I still want to KNOW that the failure happened, would Access still be expected to tell me? Would I need to use a currentdb-set variable and then check recordsaffected vs. records expected - would that be the only way to know?