The issue with storing an actual picture in the database, embedded, is that you will RAPIDLY run out of space in Access internal address space. That 2 Gb will dissolve in less than 1000 pictures at today's image densities.
Search this forum for two topics. First, "Image Controls" - we have had many posts on the subject including a couple of my own posts. Second, "Common Dialog" and "OpenFile Dialog" have been posted as well.
So... what you do is build you a database with a field for the file name and path. Usually, if you put the pictures in a folder near the root of your disk, that means shorter paths. 64 characters might be plenty.
Next, build your form. create the image control. You might have to play with the properties for zoom, stretch, etc. But to prevent bloated databases that become impossible to use, DO NOT EMBED YOUR IMAGES.
Ok, still in forms design mode, open the properties for the form itself. Under form events, select the OnCurrent event. The line of code suggested above should go as perhaps the only line of code in the forms.current event. To browse using the OpenFile dialog, you will have a control CLICK event. As the closing line of that event, if the status returned from the control indicates that it selected a file, that file name can be copied to the record. When you store it in the underlying record, also store it in the image control's .picture property and do a me.repaint.
But do the research so you will see the many variations that have been tried and the pitfalls that go with them. This doesn't have to be hard if you keep it simple in terms of goals. Further, once the image referece (file path & name) have been stored once, it is a set-and-forget operation.
In answer to another question, you can have any type of image file for which you loaded that type of image translator when you loaded MS Office. You can RELOAD image handlers - just RELOAD Office and take the Custom option to install extra features. If you have a type of image that Access does not recognize, you might have difficulty. But Access has a pretty darned good set of image handlers.
