Evan
Option 4 is probably your best choice, but, is there any way to validate that data when you migrate it? That would be the best option of all. If you can get the bulk of the invalid data fixed at that point, there would be relatively few records for the users to deal with.
>
>4) Detect if the user has changed the data, if he/she hasn't then don't validate it. Currently, I validate the data whether or not the user has changed it. This could be the root of my problem.
>Downsides:
>- I can't see any at the moment... perhaps the downside is that the users will never be told that old records are bad and thus never fix them.
>
>Optino #4 is looking like the best so far. Any better ideas?