"John Taylor" <ja**@iinet.net.auwrote
However; I have been working on a membership
database where I "hold" a photograph in a table. All
is working as would expect so I won't bore you
with the details - it works almost identically to the
Northwind sample database "employee" table.
My problem that I get an error when I have about
30 photographs attached - "database has exceeded
size limits" or something like that. I know the
database is getting big (around 1G) and perhaps
W2000 can't handle this size.
The sample imaging databases (applicable to Access 2003 and earlier
versions) 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.
Not included in the sample is the option of using the "FollowHyperlink" (for
which see Help) to display an image for which you have the
path-and-filename. Doing so will display using the image-handling software
that the user has registered for the image file type, but seems to have
fewer difficulties, all in all, than OLE Objects and Bound OLE Frame
Controls present.
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.
Larry Linson
Microsoft Access MVP