Problem ID: 7612217920589669178
Entered by: Ben Simo

Useless and Unknown

Got this trying to apply a filter to data in an Access 2003 data table.

If it really is unknown, how does Access know there is something worth reporting to the user? And if there is something worth reporting to the user, why not report it?



June 7, 2009 at 5:33 PM  
Comment ID: 5857950551089978464
Written by: Anonymous

I selected yes for this being a bug but it easily could have been a maybe. It appears that the user hit a sequence int he decision tree that got caught by the exception handler. So there was a case that the developer did not know or think about but at least they had a way to handle it. the next step is to be repeatable and create a case to handle the situation created. At some companies I worked at this would be an enhancment.

June 19, 2009 at 9:39 AM  
Comment ID: 2499300984622249394
Written by: neochance

I think this is clearly a bug and should be either hidden or communicate something relevant.

However, that's not what I find interesting. What I find interesting is there's a system close button and an ok button that are both active and can be clicked. I'd be willing to be bet that they would do the same thing (close the dialog and then do nothing). The thing is, they imply different actions, when I click the close button, the expectation is that you're going to cancel the action that produced the error and if I clicked the OK button, I would accept the action that needed to be taken to resolve the issue.

October 1, 2009 at 3:02 AM  
Comment ID: 8428501080309841488
Written by: Unknown

It is indeed a bug. No doubt.

Something interesting apart from the message "unknown" would be, what would happen if I click on close('x'). Any different effect than OK? If not, why enable it?

Post a Comment