No. It is a different program to view images. Also forgot to say that
it is on two different computers (see message below xp on one, 2003 on
the other). The display is an unbound image control that I am
inserting the link to. I did mean the same thing by blows up. Sorry.
Thanks again.
Larry Linson wrote:[color=blue]
> Is the very same program registered to be automatically used for that image
> file type on the computer that has the newer version of Access? One of the
> points was that it is not just Access that you are dealing with, but the
> image processing/display software that is registered for the image type.
>
> Still, you did not answer my question. We ask questions to try to get enough
> information to be of help. It makes a difference _how_ you are trying to
> display the image. We do our best, here, to answer specific questions, but a
> newsgroup isn't suitable for a lengthy tutorial on image handling -- that is
> why I created the examples I referenced, and why others have created
> examples of both similar and different approaches.
>
> Now, you say "blows up" but seems, before, you said "just shows the text of
> the filename." There's quite a difference between those, in my view.
>
> Larry Linson
> Microsoft Access MVP
>
> <needin4mation@gmail.com> wrote in message
> news:1150255842.365839.47290@f6g2000cwb.googlegrou ps.com...[color=green]
> > But why would I be able to see the image if another version of Access
> > inserted the image? It only blows up when the newer version inserts
> > the image.
> >
> > Larry Linson wrote:[color=darkred]
> >> What kind of Control are you using? If it is a Bound or Unbound OLE
> >> Frame,
> >> then you need to look also at what program is registered for the type of
> >> image file, because that is what does the displaying in OLE Frames.
> >>
> >> 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
> >>
> >>
> >> <needin4mation@gmail.com> wrote in message
> >> news:1150234596.618502.85160@y43g2000cwc.googlegro ups.com...
> >> > Hi, I have an Access 2002 - 2003 database. I am using Access 2003.
> >> > Whenever I link an image all it shows is the filename. Not the image.
> >> > Other versions of Access can link the image just fine. The properties
> >> > look the same whether I use XP or 2003 versions of Office.
> >> >
> >> > If I take an earlier version of Access and link the image, it puts the
> >> > image. I can also see the image in 2003. If I link the image using
> >> > 2003 it only shows the filename. If I view that same record in lower
> >> > versions it also shows the filename. In other words, if I do not
> >> > insert the object (link, not embed) with a pre-2003 version, it only
> >> > shows the filename. It has the right path and all, just will not show
> >> > on the form (other than the name).
> >> >
> >> > Thank you for any help.
> >> >[/color]
> >[/color][/color]