Access doesn't store image information very efficiently--
leading to database bloat or lo res images.
The best thing to do is store them outside of Access into
a directory path that doesn't change. Then, get each
image as needed and display it--this way, it doesn't
affect the size of the database. Name each image the same
as the primary key.
Here's how I did it:
In the Form "On Current" event is the following:
Dim OLEpath$
On Error GoTo errhnd
'if the form is in Datasheet view, exit sub
If CurrentView = 2 Then
Exit Sub
End If
'build path including primary key field
OLEpath$ = "c:\images\" & Me.txtPARTID & ".jpg"
Me.OLEimage.Picture = OLEpath$
Me.OLEimage.HyperlinkAddress = OLEpath$
Exit Sub
errhnd:
If Err.Number = 2220 Then
'if image not available, show nothing
Me.OLEimage.Picture = ""
Me.OLEimage.HyperlinkAddress = ""
Exit Sub
End If
Hope this helps!
-----Original Message-----
I have embedded JPG images via the Insert Picture control
but the quality is unusable when viewing over Terminal
Services. When I use the same control, but embed a BMP,
the quality is acceptable. I expect some degradation
since TS only allows 256 colors, but all of my pictures
are JPGs.