Re: Help Needed ASAP

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Ken Snell [MVP] (kthsneisllis9_at_ncoomcastt.renaetl)
Date: 01/28/05 

Date: Fri, 28 Jan 2005 18:35:44 -0500

In the report, you can put an image control in the Detail section. You'll
need to set it to an image path initially, but we'll use code to modify it
for each record in the report's recordset. Name the Image control
imgPicture.

Also put the field that holds the path to that record's image on the report.
Name it txtImgPath and make the control invisible.

Then, in the Format event of the Detail section for the report, use code
similar to this:

Private Sub Detail_Format(Cancel As Integer, FormatCount As Integer)
Me.imgPicture.Picture = Me.txtImgPath .Value
End Sub 

-- 
        Ken Snell
<MS ACCESS MVP>
"nutmeg@questions.com" <nutmegquestionscom@discussions.microsoft.com> wrote 
in message news:B0280E4D-1CCF-45FB-821C-2CB77B77CCD9@microsoft.com...
> Thank you, I think I may just about be understanding but not quite yet.  I
> have a form, with at the moment, an OLE frame (we do not necessarily have 
> to
> see the picture on that form, we are just using the form to attach the
> picture to it).  We then have a report that the pictures do show up on 
> that
> has to be output to a customer in a PDF format so that they can see the
> details on the form above and the picture on the bottom of the form.
>
> I am not sure what you mean about using a command button to access them, 
> but
> would be able to explain a bit more about that.  Maybe it's the setting 
> the
> picture property.....thank you for your help, I'll watch for your 
> response.
>
> Regards,
> IEJ
>
> "Ken Snell [MVP]" wrote:
>
>> No, you would use a text data type field, not an OLE field.
>>
>> Then, depending upon how you want to display the image, you use 
>> programming
>> to "get" the picture and display it. This can be done by using
>> FollowHyperlink via a command button, or by setting the picture property 
>> of
>> an unbound image control to that path, or other ways. Would need to know
>> more about what you're doing to give you more info.
>> -- 
>>
>>         Ken Snell
>> <MS ACCESS MVP>
>>
>>
>> "nutmeg@questions.com" <nutmegquestionscom@discussions.microsoft.com> 
>> wrote
>> in message news:771CE25A-E33F-4298-B59B-55EE36E9D32D@microsoft.com...
>> > Dear Ken, Thank you, may I ask for a bit more information on what you
>> > mean.
>> > Do you mean actually typing the location name in i.e.
>> > X:\SurveyDatabase\Pictures\1234.JPG into the Image OLE field?
>> >
>> > Thanks,
>> > IEJ
>> >
>> > "Ken Snell [MVP]" wrote:
>> >
>> >> ACCESS stores images very poorly... essentially in an uncompressed 
>> >> format
>> >> and then some.
>> >>
>> >> Better to store the location of an image file in a table field, and 
>> >> then
>> >> go
>> >> get that file when you want to use it by using the location from the
>> >> field.
>> >>
>> >> -- 
>> >>
>> >>         Ken Snell
>> >> <MS ACCESS MVP>
>> >>
>> >> "nutmeg@questions.com" <nutmegquestionscom@discussions.microsoft.com>
>> >> wrote
>> >> in message news:C9F01C45-F3C5-4C39-A7F7-5F46D2412E11@microsoft.com...
>> >> > We have the need to attach pictures in .JPG format to a form.  We 
>> >> > are
>> >> > using
>> >> > the Insert Object, Link and attaching them, they then appear as
>> >> > Microsoft
>> >> > photo 3.0...What is happening is the back end file has ballooned to 
>> >> > a
>> >> > massive
>> >> > size, at present 2.9 Gigs.  I tried to compact it and get an error
>> >> > message
>> >> > that says 'invalid argument'.  Can anyone help me to understand why 
>> >> > the
>> >> > file
>> >> > has gotten so out of hand and how to stop it.
>> >> >
>> >> > Thank you,
>> >> > IEJ
>> >>
>> >>
>> >>
>>
>>
>>
Quantcast