Image Quality when using linked images

The quality of the image depends on how you save it. A higher resolution image will look better, but it will aslo take up more space.

Addtionally, you will need to plan on testing the links to see if they are still valid. Links have been known to vaporize.:)
 
The images are BMPs, and when embedded within access, they are fine both in the forms and on reports. I ahve not yet tried printing a report, but I have to change them to take note of the difference as when embedded I was using OLE objects, no it is a Image box which is linked.

The quality on the form looks like the image is running on a computer with 16 colours running, very pixelated, and not at all clear.
 
Have you checked the video card settings? Right click on an empty spot on your desktop and then click on "properties". That should bring up your display settings.
 
LOL, you are missing the point, my computer is running 32bit colour, its just the image when it is linked looks as though its 16 colours.
 
That you were already in 32bit color mode was undisclosed. Did you right click on the image itelf and check its properties? If you did and its set to 32bit color then the problem is beyond level of understanding.
 
photoexample.jpg


Here is an example. I used a screenshot to capture the 'bad' image. Below is the good image which you can see is fine.

The persons head is chopped off for confidentiality reasons, but his coat indicates the issue I have I think.
 
The fall-off looks pretty bad. I have not had this problem. The images that I have used have looked fine. I will have to "punt" on this. Anyone else.
 
I have updated a report now so it uses the linked image. In preview, the picture is still bad, but when it goes to print, its fine. THought I would mention it in case it was a help.
 
The issue MIGHT be sizing. When you expand or shrink an image, you are dealing with rendering routines. There is ALWAYS exactly one and ONLY one size where the image looks 'right' and that is when the dimensions of the viewing area have exactly the same number of pixels as the original BMP (or any other) image stores.

That is, if you have picture taken by a digital camera and you crop the image to 1024x728, it will look good only if the image is displayed in a 1024x768 window. Otherwise, you have either PIXELATION (for displaying in a too-large window, caused by having to decide which bit to display on screen pixels that don't exactly overlap an image pixel) or OVERLAY (for displaying in a too-small window, caused by writing more than one pixel from the image onto the same pixel on the screen.)

Before you go accusing Access of doing something nasty to your image, consider whether it is possible that you have a size mismatch. If so, it could very well be WINDOWS that is eating your socks - via the display driver.
 
Doc, what you say does make sense. It is a good explaination as to what the problem could be. I am relatively happy as the print quality is good, and that is really where it has to be due to making sure the right person gets the paperwork, and some people that work for us find names difficult to grasp, so a picture there can be no confusion, I will have a play about with the image box to see if making it a little larger helps.

Its just odd how it does it with linked images, not embedded, but I suppose it will be down to the way it handles them.
 

Users who are viewing this thread

Back
Top Bottom