That's close to what I'm looking for. How do you handle memo fields? Is there a way for the user to review their text contents?

>A while back I created a method for users to take duplicate records and merge them into one. Not exactly the same case, but close.
>
>An image of it:
>
>http://www.postyourimage.com/view_image.php?img_id=QHWpesNscNCbgW71195588705
>
>It is created dynamicly based on what fields are in the table and if the values are different. The form shows vertical scroll bars if needed. The user can select to keep a value from either table or enter their own value. The 3rd column shows what the new record will look like if merged.
>
>A couple things that make it more user friendly:
>
>Using caption/labels to replace the actual field name.
>Using a "Conversionfunction" to take something like an employee ID and show the employee name.
>
>
>
>
>>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.