>I agree with others here, and suggest you get Cooper's book 'About Face'. Regarding your particular application, I daresay it's important to make it easy to use the application with the business rules in place.
>

The reason I brought this up was more from a desire to hear how/what other people handle in all these situations. It is easy to complain that software X isn't easy to use, it's much harder to decide how you could make it easier. Easier for the majority not for a few people. That's why I mentioned the prompt boxes for saves/closing as an example of differing opinions.

>Where it may have previously been possible for users to type in any value they like, you have tested these values for correctness AFTER the work is done. Not knowing anything about your app, I might ask how would you design the interface differently so that correct entries are easy to enter, and incorrect entries impossible to enter? This might require more picklists, disabled entries, or perhaps even an entirely different schema for the user to relate to the data.
>

This was actually a band-aid(TM) to an existing Clipper application. The types of changes we really would need to make are being incorporated into a new VFP application. I've actually redesigned the whole process so that the type of mistakes they were making are a lot harder to make. This was a situation where letting them fix things later when they had more information (ie. trying to be user friendly) was causing us problems because people were using it to not check their work.