In design view, define a field in the table as type OLE Object. TO insert the picture, open the table, point to the field and use the Insert Object menu options.
Personally, I prefer not to hold the image in the database itself; it makes it too big. My preference is to hold only the path and name of the file, and then render the image if and when required from this filename. Cheers,
Steve Lewy
Solutions Developer
steve@lewycomputing.com.au
If you want to get really smart, you store the path, then concatenate part of the file name which you can perhaps be a variable in an Access table and finaly concatenate the".jpg" as a final string.
Agree with Steve re not putting pics in table. Access is an extremely inefficient way of storing graphics.
Mikey,
The old ease vs flexibility tradeoff. If you want to get really, really smart, you do as Mikey says, but you also (a) allow optional addition of a path as part of the filename, and (b) a file extention as part of the filename. (c) You use these optional additions instead of the defaults when they are provided. This provided the best of both worlds; ease and flexibility (flexibility in the sense that you can include different types of images, and they can be located in different folders).
Cheers,
Steve Lewy
Solutions Developer
steve@lewycomputing.com.au
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.