help on image control

[rmanchu]

am using access 2003 with sql server 2000

i have a product table that stores a picture of the product (as an
IMAGE type field). what is the best way to handle this field on an
access form?

wud using and OLE Object field be a problem? (i ask cos i i've seen
posts of how the file gets inflated when using MDB, but i'm using SQL
Server?

i cud then write some code to display the pic in an image control? wud
this be an efficient solution?

also is there a native Access FileChooser control? i'm thinking of
hiding the "ugly" OLE-Control with the FileChoosr and Image controls
visible.

please give me a good idea on this.

riyaz

 

[Arvin Meyer [MVP]]

Try storing just the path of the image in a database text field. Then load
on demand the image in an Access image control. While the database is in
JET, my website has an example which works equally well in SQL-Server:

http://www.datastrat.com/Download/Picture2K.zip

There is no native Access File chooser. I use use the API:

http://www.mvps.org/access/api/api0001.htm
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[rmanchu]

hi

r the images stored on the database? i ask cos, u mention that i shud
store the path which leads me to believe that images r stored
separately

riyaz

 

[Arvin Meyer [MVP]]

Yes, the images are stored outside the database. That is the way I prefer to
srore them as they can be used anywhere. There are various methods of
storing them inside the database. Some cause extreme bloat, some do not, but
all of them use much more space than storing the path.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[Larry Linson]

r the images stored on the database? i ask cos, u
mention that i shud store the path which leads me
to believe that images r stored separately

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.

Larry Linson
Microsoft Access MVP

 

[Guest]

"(e-mail address removed)" a scris: