>>I would appreciate any thoughts or advice on user interface design. I have an app in which the user edits must be approved by a supervisor before they are allowed to be merged into the "official" data. This is accomplished by saving the edits into a series of "pending edits" tables which are then reviewed by the supervisor. My problem is in how to present these pending edits to the supervisor. The data types extend to pretty much the full range of standard fields IE: CNIDM. In the edit review form, we want to show the supervisor both the existing value and the proposed value for the field and give him/her the option to approve/disapprove the edit one record at a time. The supervisor has the option to make partial approvals of some field edits while excluding others. I have drafted a form that does this by collecting the before and after values into memo fields and presenting them in side by side comparison editboxes with a button to approve the edit to the particular field. but it
>>appears clumsy to me and I am looking for a cleaner design. I would think others have dealt with this situation and was wondering how it was approached.
>
>Would it work for you to use something like the normal data entry form, but perhaps doubled with the old value showing above or below the new one? You could use color or bold or something to indicate the changed fields and put a checkbox next to each changed field to indicate whether or not to accept the change.
>
>Seems to me you could even write some code to generate the form dynamically.
>
>Tamar

Thanks Tamar. I have pondered that but the mainform is maximised and packed full with 2 page frames and very many fields. Literally no room for additional comparison fields. Its well organized but really full. I could probably design a new form(s) specific to the tables and fields being reviewed but I was hoping to do it with a single multi purpose form. I may end up with a series of edit review forms as you suggest if I can't find a more generic solution.