If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Image Handling in an Access Database
I'm using Access 2007 to develop a simple personnel database.
One of the fields in the main table is an OLE object which has been used to store an image of each staff member. Up to now, the users access the table directly and paste the image in from an open word document. There is also an associated form that allows the users to update some (not all) of the numeric and string data. I've been asked to tidy up the application so I'd like to include the image in the data entry form with a browse button so it can be replaced by browsing to an alternative jpeg file. I suppose a remove button would also be useful. The form is used for entering new records as well as modifying existing ones. I've spent a hour or so googling around but can't find anything that fits my requirements exactly. I don't suppose any of you would have a simple solution handy or can point me in the right direction? It's important that the images are stored within the database and I would like the solution to work in older versions of Access (2000 and 2003). Thanks in advance, Dave. |
#2
|
|||
|
|||
Image Handling in an Access Database
For 2003 and older, storing the images IN the table was a definite "don't do". One of the worst problems was exponential bloat (far greater then the image size). The answer was t store the image as a seperate file, to store the file name and location in 1 or 2 fields, and use code to display the image in a form or report. So, if you are really going with "work with older versions" this is your only viable way. I heard that 2007 solved the exponential bloat problem. |
#3
|
|||
|
|||
Image Handling in an Access Database
Thanks for the reply Fred.
Trouble is that this is an existing system so I don't want to change it too much to avoid alienating the users who built it in the first place. The other problem is that we don't have an enduring solution for storage of the database so it'll have to move in the near future so separate images would make this more difficult. I think I can cope with the issue of bloat by making sure that the images aren't 12 megapixels but something more appropriate for a 4 inch preview. |
Thread Tools | |
Display Modes | |
|
|