Poor error handling in Access - it's like going back in time. Anyone agree?

[whitespace]

I'm sick of the lame excuse for error messages that Access gives out.. I'm talking about 'Overflow', 'invalid use of Null' and such like.

What about telling you what field/expression caused the error and on what record if applicable.

It's so frustrating - Access obviously knows what caused the error but refuses to tell you so you have to go through the annoying process of taking out fields one by one (when in query view).

Does anyone agree that they need to make the error handling in Access much better?

Thanks for any interest in my post.

 

[Oldsoftboss]

I think whitespace is referring to the vauge msg Access often gives, not the error trapping process. We probable notice it more during the de-bugging process as programming will often bring unexpected results. Once the errors are ironed out, the stanard user will rarely get an error msg, or get a custom msg that you have created after sorting out the BS.

Dave

 

[whitespace]

thats right oldsoftboss, I have used error trapping within vba - and that's fair enough because it's up to you to control it...

What I am talking about though are the standard Access errors - They are very unhelpful - and should really - in this day and age be a lot better.

They give you no idea of what caused the error - for example on a query with 30/40 complex calculated expressions looking at vba functions etc. and you get a 'Overflow' error - and that literally is ALL it says!!!!! If it at least told you the field that was giving the error - and then if applicable the record number that caused it to fall over or something (in some errors)- does anyone know what I mean?!