By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,476 Members | 889 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,476 IT Pros & Developers. It's quick & easy.

Storing OLE

P: n/a

Re: storing jpg images in Access.
I have a database that requires adding pictures (jpegs) on a regular basis.
OLE field.
Even if they are only 320x240 large, I can see - over time, that the amount
of space these pics will take up will be great.
Does linking the pics still copy these pics in the database?
Any suggestions on a practical approach to keeping the database functioning
smoothly over the coming years with the regular addition of pics on a
regular basis ?
thanks
Nov 13 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
where's Larry Linson's canned response to this?
Short answer - don't store your images in the database, just link to
them. You can use the OpenSaveFile API to grab the path to the file
see the API section of www.mvps.org

Nov 13 '05 #2

P: n/a
<pi********@hotmail.com> wrote in message
news:11**********************@l41g2000cwc.googlegr oups.com...
where's Larry Linson's canned response to this?


You mean:

The sample imaging databases at http://accdevel.tripod.com illustrate three
approaches to handling images in Access, and the download includes an
article discussing considerations in choosing an approach. Two of the
approaches do not use OLE Objects and, thus, avoid the database bloat, and
some other problems, associated with images in OLE Objects.

If you are printing the images in reports, to avoid memory leakage, you
should also see MVP Stephen Lebans' http://www.lebans.com/printfailures.htm.
PrintFailure.zip is an Access97 MDB containing a report that fails during
the Access formatting process prior to being spooled to the Printer Driver.
This MDB also contains code showing how to convert the contents of the Image
control to a Bitmap file prior to printing. This helps alleviate the "Out of
Memory" error that can popup when printing image intensive reports.

If you've already starting storing images in your database, and you'd like
to export them all, see: http://www.lebans.com/oletodisk.htm

<g>

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


Nov 13 '05 #3

P: n/a
Yep, thanks Doug. That's the one.

Nov 13 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.