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

Strange Access 97 Behavior in Displaying Images

P: n/a
At first I was not certain what could cause Access 97 from displaying
most jpeg images, but not all. After further testing, it seemed that
all original images of less than 275 pixels per inch or less would
display, but those close to 300 pixels/inch or greater would not (MS
Access cannot recognize the file format xxx.jpg). The larger, original
images were scanned and saved as .bmp (at 300 dpi producing a 15MB
file). Then the images were saved as .jpg's around 1MB, and adjusted
downward, but no luck. However, MS Photo Editor would open the larger
jpeg file size images consistently.

Is this strange behavior or what? Has anyone experience this problem?
Any insight and tips will be appreciated. Thanks.
Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
No, I have not. And I believe I have displayed some 1 MB or near-1 MB JPG
files. Were you displaying in OLE Frames or Image controls? If the latter,
there's no question in my mind that the "graphics filters" are less capable
than typical image processing software, such as MS Photo Editor.There are
sample databases at http://accdevel.tripod.com that illustrate three
approaches to handling images in Access.

Larry Linson
Microsoft Office MVP

"Dalan" <ot***@safe-mail.net> wrote in message
news:50**************************@posting.google.c om...
At first I was not certain what could cause Access 97 from displaying
most jpeg images, but not all. After further testing, it seemed that
all original images of less than 275 pixels per inch or less would
display, but those close to 300 pixels/inch or greater would not (MS
Access cannot recognize the file format xxx.jpg). The larger, original
images were scanned and saved as .bmp (at 300 dpi producing a 15MB
file). Then the images were saved as .jpg's around 1MB, and adjusted
downward, but no luck. However, MS Photo Editor would open the larger
jpeg file size images consistently.

Is this strange behavior or what? Has anyone experience this problem?
Any insight and tips will be appreciated. Thanks.

Nov 12 '05 #2

P: n/a
The core issue is that all non Bitmap/DIB Images are converted to
Enhanced Metafiles before they are displayed in the Image control. For
certain versions of WIndows there is a 16MB limit on any embedded DIB's
within the metafile. I cannot find my original notes but I think any
native JPEG larger than around 2200 *2200 would fail to load.
To get around this issue either:
1) Upgrade the OS to XP
or
2) Convert your JPEG's to Bitmap/DIB
or
3) Use the LoadJpegGif solution on my site which bypasses the Office
Graphics filters.
http://www.lebans.com/loadjpeggif.htm
A97LoadJpegGif.zip is a database containing a function to allow for the
Display of Jpeg and Gif files on systems that do not have the Office
Graphic Filters installed. Here is the A2K version: A2KLoadJpegGif.zip

NEW - April 05 2003 Ver 5.0 Developed to allow Access RunTime
installations to display Jpeg files in a standard Image Control.
Provides functionality to load JPG,GIF,BMP,EMF,WMF,CUR and ICO files on
systems without the Office Graphics Filters loaded.
Originally developed for Systems with Access Runtime only. Supports
transparency in Transparent Gifs. Allows you to resize Images on
Forms/Reports at runtime with no loss of Image quality.

FInally take a moment to read the Image FAQ on my site here:
http://www.lebans.com/image_faq.htm

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.
"Dalan" <ot***@safe-mail.net> wrote in message
news:50**************************@posting.google.c om...
At first I was not certain what could cause Access 97 from displaying
most jpeg images, but not all. After further testing, it seemed that
all original images of less than 275 pixels per inch or less would
display, but those close to 300 pixels/inch or greater would not (MS
Access cannot recognize the file format xxx.jpg). The larger, original
images were scanned and saved as .bmp (at 300 dpi producing a 15MB
file). Then the images were saved as .jpg's around 1MB, and adjusted
downward, but no luck. However, MS Photo Editor would open the larger
jpeg file size images consistently.

Is this strange behavior or what? Has anyone experience this problem?
Any insight and tips will be appreciated. Thanks.


Nov 12 '05 #3

P: n/a
"Stephen Lebans" <Fo****************************************@linval id.com> wrote in message news:<3S*********************@ursa-nb00s0.nbnet.nb.ca>...
The core issue is that all non Bitmap/DIB Images are converted to
Enhanced Metafiles before they are displayed in the Image control. For
certain versions of WIndows there is a 16MB limit on any embedded DIB's
within the metafile. I cannot find my original notes but I think any
native JPEG larger than around 2200 *2200 would fail to load.
To get around this issue either:
1) Upgrade the OS to XP
or
2) Convert your JPEG's to Bitmap/DIB
or
3) Use the LoadJpegGif solution on my site which bypasses the Office
Graphics filters.
http://www.lebans.com/loadjpeggif.htm
A97LoadJpegGif.zip is a database containing a function to allow for the
Display of Jpeg and Gif files on systems that do not have the Office
Graphic Filters installed. Here is the A2K version: A2KLoadJpegGif.zip

NEW - April 05 2003 Ver 5.0 Developed to allow Access RunTime
installations to display Jpeg files in a standard Image Control.
Provides functionality to load JPG,GIF,BMP,EMF,WMF,CUR and ICO files on
systems without the Office Graphics Filters loaded.
Originally developed for Systems with Access Runtime only. Supports
transparency in Transparent Gifs. Allows you to resize Images on
Forms/Reports at runtime with no loss of Image quality.

FInally take a moment to read the Image FAQ on my site here:
http://www.lebans.com/image_faq.htm

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.
"Dalan" <ot***@safe-mail.net> wrote in message
news:50**************************@posting.google.c om...
At first I was not certain what could cause Access 97 from displaying
most jpeg images, but not all. After further testing, it seemed that
all original images of less than 275 pixels per inch or less would
display, but those close to 300 pixels/inch or greater would not (MS
Access cannot recognize the file format xxx.jpg). The larger, original
images were scanned and saved as .bmp (at 300 dpi producing a 15MB
file). Then the images were saved as .jpg's around 1MB, and adjusted
downward, but no luck. However, MS Photo Editor would open the larger
jpeg file size images consistently.

Is this strange behavior or what? Has anyone experience this problem?
Any insight and tips will be appreciated. Thanks.


Thanks Larry and Steve for your suggestions. I am using a Windows 98
SE machine. Any and all BMP's that I have attempted to display in
Access have been extremely poor quality although the source images
were sharp. I'm just using small pieces of code for displaying as an
"Image", browse for file, and linked only and with photo path shown -
all independent of Access' built-in features for image display. What I
have discovered though is conflicting to what I have read regarding
the Runtime version needing supplemental graphic filters to display.
I have installed my Runtime version in tests on several machines with
different OS' a couple with different versions of MS Office (Access)
and a few with no MS Office installed at all. On every machine the
standard test jpeg images were displayed properly - how can this be?
My assumption has been that if other photo imaging software is
installed then the image display has been through utilization of
non-MS graphic filters - is this possible?

I will take another look at your LoadJpegGif solution Steve to see if
I can incorporate a workaround for the larger images. Thanks.
Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.