For all versions of Access prior to Access 2007, images are generally not stored in an MS Access table because of the ole bloat problem discussed by Neil. Generally only the path to the image is stored in an Access table, and the images are retrieved from the path for display via an Image Control on an MS Access form or report. To compensate for the limitations of Access, most Access developers embraced the free utility functions provided free by Stephen Lebans for Access versions prior to 2007.
Stephen Lebans haa provided a utility function that allows you to save ole images to disk, thus mskes it easier to retrieve ole images from the disk so they can be viewed in Access
http://www.lebans.com/olet
He also has provided a utility function that allows the image to be compressed as a jpg, thus avoiding the bloat problems associated with storing the image as ole in an MS Access DB.
.
http://www.lebans.com/load
Main Topics
Browse All Topics





by: neil_squiresPosted on 2009-10-19 at 21:16:25ID: 25611029
I believe it is best practice to not embed pictures in an access database. On version 2003 and older it would cause exponential bloat. For example, a 30k picture would cause the database to grow in size by 10 megabytes. I recommend storing the images in a directory and then storing a path to them. I believe you can use an oledb object to point to the file path.
Does this help?
Neil Squires