Quote:
Originally posted by postal postie:
<BLOCKQUOTE>Originally posted by Neyles: postal postie
You show me someone with a workaround and I'll show you someone else, who cannot replicate it. This indicates something is seriously off. I refuse to believe that all can be assigned to user error; the workarounds are not that complicated. I suspect that SI don't know the full extent of the problem, a worrying fact considering the FM08 release date is a dim memory. I just hope that the next FM installment won't cause as much trouble. |
obviously the problem can be put down to poor coding as you should not allow the user to do anythign which could cause an error.
for example if you have a program where you type in two prices and get it to caluclate the total you dont want them to be able to do the sum
'hello' + 2
otherwise it comes up with an error.
so you set validation or you funnel the user down a specific path, MAKING them do what ever it is at the time that you want them to.
i agree that it's not perfect but if SI believe that there is a specific workaround and they know for a fact that we can perform the workaround every single time then great. </BLOCKQUOTE>
PP - I believe what you're talking about is known as "error trapping", i.e. not allowing the user to make an error. I'm involved in the testing team for our software where I work (I was overlooked for the SI testing team

) and I've noticed that gaps in error trapping are more common than any other limitations in the software. It happens unfortunately.