what error numbers will CurrentDb.Execute strSQL,dbFailOnError raise?

hey guys,

i'm trying to write an error handler for the rollback of a transaction and instead of writing a generic catch everything error handler, i would like to handle specific errors that will be raised by dbFailOnError.

hrmm from what i read there could be a few / a myriad of errors raised.

does anyone have the list of errors that dbFailOnError could raise?

if not, could you advise me how i can handle the error specifically? thanks guys!! = ))
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rey Obrero (Capricorn1)Commented:
the dbFailOnError option generates a run-time error and rolls back all successful changes if any of the records affected are locked and can't be updated or deleted.
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
"there could be a few / a myriad of errors raised."

"does anyone have the list of errors that dbFailOnError could raise?"
Doubtful - because there are sooooo many possibilities.

However, there is good news. Depending on exactly what you are doing - for example - executing an Update query - one error you would want to trap for sure are is Write Conflict error (there are a couple) ... so, for a given situation, you do not need to cover 'everything' - IE,  errors that might occur for a delete execute - might occur for an Append execute.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
developingprogrammerAuthor Commented:
thanks capricorn1! yup the availability of locks is very important in dbFailOnError! = )

ah i see, thanks mx! definitely agree with you that we can try to gear ourselves for the main errors. hrmm, but i think what i'll do is create a sub function for this if it's very critical so i know that all errors raised in the sub function is a result of the things inside the transaction. thanks mx!! = ))
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.