images in Access 2003 with no Photo editor

[Guest]

I understand you have to install photo editor from Office 2000 in order for
images to work in Access 2003. I don't have Office 2000 my system came with
2003. What do I do now? Is there a work around to get images to appear
without Photo Editor?

 

[Guest]

No you don't need photo editor - it one of the worst photo manipulation
programmes there is so you are better off without it anyway.

If you want to view pictures in an access form or report there are many
posts on this site telling you how to do this. BUT you will need to have
pictures that are supported by access - for most people this will not problem
so have a look around this formum and you will find loads of post about
viewing pictures in access - my one tip is to link rather than embedd

 

[Guest]

I am linking not embedding. I am using .bmp files. Still have trouble
viewing and have looked around lots. Did not find any solutions except those
that mention photo editor. If you know of a fix I would love to hear about
it.

 

[Guest]

What do you want to do with your BMP files.

 

[Guest]

Display them in forms and reports
--
Dar

What do you want to do with your BMP files.

 

[Guest]

Bit confused - why do you need photo editor to do this.

All you need to do is create a field in your table. Insert the path of the
picture and link this to a form or report. You don't need photo editor

 

[Guest]

Wayne have you tried this? It comes across as a fuzzy image with the file
name. The suggested fix is to install Photo Editor. Photo Editor is not
something I want to use it was the recommened fix found in the help screens.

 

[Guest]

You can check out this link which on the main MS site
http://support.microsoft.com/kb/285820/en-us

Or as this question is asked many time I have given a “step by step†here.
As it’s a “cut and paste†you may not need it all but I hope it helps you
along in the right direction.

. . . . . . . . . . . . . .
You need to save the original picture on your hard drive and simply show a
“thumbnail†Bitmap copy of this on you form that could be used “as-is†or
maybe as a hyperlink to open the main picture (using OnClick)


Make copies of the pictures you want to link to your records (on C Drive /
hard disk) and save them as
ThumbnailPicture1,
ThumbnailPicture2,
ThumbnailPicture3,
etc, (or use the ID of the record in the table)

If you have a picture processing programme then use that to resample and
convert. If you don’t follow this

1 Click start
2 Click My Pictures (if that’s where they are)
3 Right click the picture and select “Open Withâ€
4 Select Windows Office Picture Manager
5 After the picture is open click the Picture Menu then select Resize
6 Resize your picture to the correct size
NOTE. You will need to know the pixel size of your OLE box - see below
7 SaveAS a copy of the original (DON’T JUST SAVE or you will ruin the
original picture)

BMP Windows Bitmap this is best option
GIFF CompuServe Bitmap is also OK
JPEG’s “will†work but they are not really meant for this type of
application REMEMBER that JPEG’s are reducing formats – so each time you
change and save you will lose some resolution.

Create an OLE field in the table (use this OLE field on your form if you
wish to display the picture on a form with a particular record)


To link your picture thumbnail with the OLE
8 Open the Table that will hold the data /picture (not the form)
9 navigate to the OLE field on the correct record and Right Click
10 Select Insert Object
11 Select Create From File and then Bitmap and then check the Link option
12 Browse to your picture and select it
13 Click OK
14 “Package†will appear in the field
15 View your image on the form


Some notes on the size of your OLE object – regardless of what anyone will
tell you there is no way of converting pixels to cm’s – which your OLE object
will be sized in, UNLESS you know the size of each pixel or even the screen
resolution and as screens are all different sizes and resolutions this simply
isn’t possible here, so I have given the APPROXIMATE conversions here you
will have to gig about with your thumbnail until it fits your OLE. Better
still save all the thumbnails as size that you’re happy with and resize your
OLE to fit this.
On a screen resolution of 1024 Pixels X 768 (this is standard High Res for a
lap top)
5mm = 118 Pixels or 14.173 Points
1cm = 236 Pixels or 28.346 Points
So you can work out that say 3.5cm would be 827 Pixels or 99.213 Points


Hope this helps and points you in the right direction

 

[Guest]

Thanks for trying to help, but a 15 step procedure is too much to expect the
end user of this to manage. OLE has gone from a right click insert object to
15 steps and you still end up with a fuzzy image and the name of the file.

I have tried a work around by inserting the picture into a Word document and
linking the word document. The result is a clear image on forms and reports.
So thanks anyway but I will try it with the Word doc.

 

[Guest]

It's not a 15 step thing - it's a 1 step

You as the programer need to do the background work - all the users need to
do is save the picture into a file on your C drive (or if on a server another
drive).

If you have done a good job you will have coded the form (on new record) to
allocated the file path for the next incremental number. All the uder needs
to do is save the picture with the same number - which all windows files will
do automatically so you don't need to worry about it. The next picture in a
file will always have an incremental number to the previous if you don't
specify another name.

Access is great (and very easy) to use with pictures.

Give it a try - you will find that once you have created the table field and
form field and the code it not a problem.

You can concencate a code together with the autonumber ID field which makes
it even easier - then you can be sure the right picture is on the right form

Give it go and see

 

[Guest]

I have a table with two fields the part number and ole field for the picture.
I go to the OLE field find the picutre that is a .bmp and link it. When I
view a report or form with the OLE field it appears as a fuzzy image with the
file name.

Have you actually done it with Access 2003?

 

[Larry Linson]

I have a table with two fields the part number
and ole field for the picture. I go to the OLE
field find the picutre that is a .bmp and link it.
When I view a report or form with the OLE
field it appears as a fuzzy image with the
file name.

Have you actually done it with Access 2003?

The samples for "Access 2000" in the following reference work with Access
2003. The problem with using OLE Object Fields, and Bound or Unbound OLE
Frames, is that you put yourself at the mercy of whatever software the user
has registered for the image file type. If you are getting a "fuzzy image,"
it's not Access' problem. "Photo Editor" was simply a COM-enabled image
processing software package included with Office Pro 2000, that was
installed, and by default, registered for many image file types. Any other
COM-enabled image processing software package can be used... but may not
give the results you'd like.

If you are not happy with the quality, and you can reset the registrations,
use a folder window, Tools | Options | Folder Options, and register your
browser . . . most browsers do a creditable job of rendering common image
file types.

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