"Naturally, if a program requests a file, and you point it to the wrong one, things won't work right. This seems like reasonable behavior to me."
I agree with you, Blue, that it is very difficult for an application developer to protect the user from all of his/her misbehavior.On the other hand, I think that UFT could use a heavier dose of self-protection code that checks for reasonableness of user entry.For example in this case if a dbf is missing and the user is asked to "find" it, wouldn't it be reasonable for the code to check to see if the selected dbf has the correct data content (field names and so forth)? Most users are baffled by the cryptic request "where is..." and so forth; a better explanation to the user of what the problem is and what to look for would seem to be appropriate.
I know the addition of such elegance is expensive in terms of programmer time and even program size, but I am confident that each little improvement along these lines pays off in reduced expense in the technical support area and in user (customer) good will (which some economists quantify in a dollar sense).
But please don't use this as a way to get more resources for engineering at the expense of current tech support.They need every brain cell they have. :-)