A familiar story Steve; I've often experienced problems similar to your wife's. But when it comes to feeding this information back to the organisation concerned I try on three different 'hats':

1) my tester hat: "it would be great to get this sort of direct feedback because it helps me to improve my test cases"

2) my developer hat: "knowing this would help me to improve my code"

3) my business analyst hat: "ah! a problem that we need to find a solution too. I know you coding guys love an SQL emergency but let's not jump the gun and assume it is a coding issue. It could be a simple data entry issue."

In the end I always opt for the last approach: present the organisation with the actual user's problem as experienced, don't try to present a solution because, as 'CirquedeSQLeil pointed out, you don't want your staff deluged with false positives. As a developer I demand the same from my BAs: "give me a problem, don't tell me (what you think is) the solution".