>Wow! This is not sounding like a trivial exersize.
>
>In addition to what everyone seems to be recommending, I will need code to allow the user to add/replace/remove a picture associated with a record. When records are deleted, I will want to delete the associated picture to ensure that there are not any orphans. I will need code to refresh the image as the user navigates through the records. It looks like I have to write code to imitate the binding process that is automatic with most other controls.

You are correct. You may also need code to restore the original image in the event that the user cancels out of a record update. In my naming-convention approach, I add "TEMP" to the name of the currently saved (permanent) image file and make a temporary copy of the image to use as the (displayed) "value" of the image control, and there is code for the CRUD operations using the temporary and permanent image files.