I'm grateful for your frank, honest,
professional assessment of the two
products. I need comments like yours
to decide which tool will suit my
customer.
Actually, it would be better if the "frank, honest, and professional
assessment" on which you based your decision were accurate and complete.
Only one of several approaches to handling images in Access suffers from the
problems that Jeremy mentioned -- perhaps it is the only approach he knows,
and thus, he damns the product on the basis of an incomplete understanding.
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. And, all three
will work in an Access mutliuser environment or in an Access client to a
server database, as well as with a single-user Access database.
* they are not the only approaches, but are
representative and are commonly-used
methods
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
