Embedding images in a database is a very self-limiting operation. You would do far better to take the approach of storing all image files in the same folder as the DB, then when you use the file-select object, just store the file name. You can always figure out where you are (in terms of current folder).
For a database-type variable instantiated via Set {myvar} = CurDB, you can get the {myvar}.Name property and parse it from right to left to determine your current directory / folder name. Then just tack that onto the file name you stored earlier any time you want to load an image.
Using OLE and pictures is not the best way to do this. Seriously. Once you reach a certain size, your performance goes to poop. And by embedding rather than linking, you reach that size faster. (Why? you ask....)
When you dump pix inside the database file, you are placing demands on physical memory. When you put ENOUGH pix inside the database file, you start paging to the swap file. This is defintely NG. Not Good. And by embedding the pix, you just about GUARANTEE you will hit that spot fast. On the other hand, linking means instead of storing megapixels in the MDB file, you store them externally and only store file-name strings. Then when you do a Form_Current routine on the form in question, you can load up the link to the {image-control}.Picture property and there you are, ready to view. Further, performance will be quite reasonable for linking.
