Microsoft Access has bad image import, and no image transparency.

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Dave - 26 Nov 2004 21:42 GMT

For some reason Access has been poorly designed when it comes to image import:

-> BMP transparency is ignored
-> PNG transparency is ignored (sadness ensues)
-> EPS files will almost always display with faulty colors and faulty paths
-> TIFFs are not support at all
-> Images will show different colors within the transparent area of an
overlaid EPS bounding box

Also, why is there no zoom in Access? Why does it always have to be one
zoom mode or print preview? This makes image work horrible.

Why is there no Lock Object feature in Access?

As powerful as Access *could* be, it's made for simple, I mean pathetically
*SIMPLE* image support. It's really a poor program if you try to do anything
worthwhile.

Dave May
Internet Effects

Reply to this Message

Larry Linson - 27 Nov 2004 02:54 GMT

Access was not, of course, intended to be "image-processing" software, but
database software. All things considered, I have been happy enough with the
imaging capabilities it provides -- one of which is to use OLE Frames to
display images in one of several ways (either from a stored OLE Object,
which can be embedded or linked, or with the file set at display time). This
will use whatever image processing software is registered for the file type
on the user's system. If you are storing OLE Objects, it also is not
"thrifty" with storage, but whatever image software you are prepared to
invest in will provide the capabilities.

In my database work, it has been quite satisfactory to save the images as
BMP or JPG, both of which work very well with Access built-in Image control
for _display_... acquiring and displaying images is all I have needed to do
with my database applications. For other image processing and modification,
I have image-processing software.

What is your definition of a "Lock Object feature"? I'm not certain what you
want.

Larry Linson
Microsoft Access MVP

P.S. This isn't a good place to get an answer to "why does" or "why
doesn't"... the Access product managers and planners are not often in these
newsgroups, and may not be at liberty to discuss the reasoning behind design
decisions, in any case.

> For some reason Access has been poorly designed when it comes to image import:
>
[quoted text clipped - 16 lines]
> Dave May
> Internet Effects

Reply to this Message

Dave - 27 Nov 2004 15:31 GMT

> Access was not, of course, intended to be "image-processing" software, but
> database software. All things considered, I have been happy enough with the
[quoted text clipped - 5 lines]
> "thrifty" with storage, but whatever image software you are prepared to
> invest in will provide the capabilities.

OLE Objects cannot have transparent areas, at all.

> In my database work, it has been quite satisfactory to save the images as
> BMP or JPG, both of which work very well with Access built-in Image control
> for _display_... acquiring and displaying images is all I have needed to do
> with my database applications. For other image processing and modification,
> I have image-processing software.

I imagine that you are not making very fancy reports. Want to put a
transparent PNG in front of some report data? Sorry, you can't.

I'm not using Access for "image processing". I'm using it to generate
creative mail pieces and statements which require subreports.

> What is your definition of a "Lock Object feature"? I'm not certain what you
> want.

Off-topic, but I would like to be able to lock items from accidental
movement. My reports are complex (mail merge letters, statements, etc.). I
wonder if Word will handle transparent images... but I know it won't handle
subreports.

> Larry Linson
> Microsoft Access MVP
[quoted text clipped - 3 lines]
> newsgroups, and may not be at liberty to discuss the reasoning behind design
> decisions, in any case.

Of course not; that would be productive.

Dave

Reply to this Message

Duane Hookom - 27 Nov 2004 16:01 GMT

Stephen Lebans has the best site regarding images and Access. He has created
many work-arounds and solutions. You might argue that some of these belong
in native Access. Of course, others might like to see more sophisticated
mail merge or better statistical analysis or tables with triggers or
one-click "build-me-an-application" or...

I personally find Access graphics acceptable and wouldn't want additional
graphics functionality to create a larger install, slower loading, and
possibly more bugs...

Signature

Duane Hookom
MS Access MVP
--

>> Access was not, of course, intended to be "image-processing" software,
>> but
[quoted text clipped - 51 lines]
>
> Dave

Reply to this Message

Larry Linson - 30 Nov 2004 01:52 GMT

> OLE Objects cannot have transparent
> areas, at all.

OLE Objects simply wrap various types of files and store them. They do not
modify the internals of the wrapped files. OLE Frames employ the registered
software to display the file from the OLE Object. It is possible, of course,
that the combination of OLE Frames and the software registered for the file
type does not support transparency.

> I imagine that you are not making very
> fancy reports.

You are correct -- my clients don't pay for "fancy", and they don't pay for
"glitz and glitter". They pay for solutions to their rather normal, modest
business issues.

> Want to put a transparent PNG in front
> of some report data? Sorry, you can't.

No, I have never had a need to use a PNG, much less a transparent one.

> I'm not using Access for "image
> processing". I'm using it to generate
> creative mail pieces and statements
> which require subreports.

It certainly reads to me that "image processing" is exactly what you want to
do. Perhaps a database is not the appropriate tool for creative mail
pieces -- or perhaps someone here could direct you to where on the Microsoft
site they maintain a "wish list" into which you could place a request for
some specific enhancements to image handling in reports.

Nothing you have described prevents using subreports.

> > What is your definition of a "Lock
> > Object feature"? I'm not certain what you
[quoted text clipped - 4 lines]
> reports are complex (mail merge letters,
> statements, etc.).

I don't think that is off-topic at all. You can prevent users from modifying
the design:

You can create an MDE, which locks down the
design view of any object that can have an
associated module -- including reports and
forms.

You can apply Access security and not give
users permission for design view, if you have
a compelling need to maintin the MDB
form. You can even use this to block yourself
from modifying the design of a particular
report. But it is not as easy as a single-click to
lock the object would be.

> I wonder if Word will handle transparent images...
> but I know it won't handle subreports.

Because Word is not a database program, I don't even see how subreports
apply. Word doesn't "handle reports", either; it handles documents. In
regard to Word handling transparent areas in images, that would be a good
question to ask in one of the microsoft.public.word... newsgroups.

> > P.S. This isn't a good place to get an
> > answer to "why does" or "why
[quoted text clipped - 5 lines]
>
> Of course not; that would be productive.

Well, it is a good thing we are at liberty to politely disagree, because I
certainly disagree. In a previous incarnation as a mainframer and
microcomputer developer, I have been involved in the architecture and design
of software. There are many, many factors in a particular architecture or
design decision, and, in my experience, the decision was recorded but not
the debate leading to it.

It would have been extremely counterproductive to put us in a position of
trying to explain and defend every design decision to anyone who chose to
second-guess, as would be the case if the Access design team responded to
"why" questions in newsgroups.

One major factor is the intended user audience; and, I suspect, developers
of creative mail pieces are a rather small part of the expected user
audience for what was, after all, thought to be just a nice little desktop
database (and surprised everyone, including its developers, with the breadth
of functionality that it actually had).

Larry Linson
Microsoft Access MVP

Reply to this Message

Stephen Lebans - 27 Nov 2004 16:17 GMT

Transparency is not natively supported except for OLE Frame controls.
There is a workaround here that can be used at runtime to load in BMP,
GIF, Metafile and Jpeg files.
http://www.lebans.com/transparent.htm

For the rest -> Answers Inline

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.

> For some reason Access has been poorly designed when it comes to image import:

Access uses the standard Office Graphics filters. Transparency is really
the only area where the functionality of the Import filters differs from
any of the other standard Office programs. This is due to the fact that
Access supports forms in Continuous view with lieghtweight controls.

> -> BMP transparency is ignored

See solution above

> -> PNG transparency is ignored (sadness ensues)

PNG is a relative latecomer to the Image file format scene. Sounds like
it is you image format of choice.

> -> EPS files will almost always display with faulty colors and faulty paths

EPS is a difficult format for all Office software.

> -> TIFFs are not support at all

Perhaps you mean multipage TIFF files versus standard TIF files? Both
formats are supported, TIF fully and limited support for TIFF. This is
to be expected and no different from most standard software.

> -> Images will show different colors within the transparent area of an
> overlaid EPS bounding box

EPS is a difficult format for all Office software.

> Also, why is there no zoom in Access? Why does it always have to be one
> zoom mode or print preview? This makes image work horrible.

There are two different "ZOOM" methods built into each image control. By
specifying the dimensions of the control you can control the output
resolution down to the pixel. I think you misunderstand this property
and its use.

> Why is there no Lock Object feature in Access?

I have no idea what you mean here. If you do not want an element of your
Report to move than do not allow any controls or sections above it to
GROW.

> As powerful as Access *could* be, it's made for simple, I mean pathetically
> *SIMPLE* image support. It's really a poor program if you try to do anything
> worthwhile.

That's a very negative statement Dave. I think you are leaving the
user(you) out of your equation.

I have used most of the major report writers that exist today. If you
check GoogleGroups you will see that the majority of Developers/Users
would vote the Access Report writer at or near the top of any ranking
list.

> Dave May
> Internet Effects

Reply to this Message