Photos and continuous form

[CEH]

I'm experimenting with a DB that contains links to photos... using the Ken Goetz code... So far very simple, one table for "People" another for "Photos" (field with links) What I have now is a button on the first form that opens the second form which displays the pictures. No using a single form I have multiple pictures for each person... so you can click from record to record to see all related pictures. What I really want to do now is design a form that displays all pictures at once for that given person. I have tried a continuous form with no luck...it does display each path to the photo correctly but displays only the same photo over and over... Any ideas or examples of what I am trying to get to?
From my searching it seems the picture is loaded from the OnCurrent event of the form...Me.Image.Picture = Me.txtPhotoPath .... And only executes once...causing the same picture to display for every record....is there a way to make this execute for every record on the form?

 

[CEH]

Bump....bump.... No one has any experience with this one?

 

[Max D]

The problem is Access doesn't create separate controls for each record - or it would hang trying to display really big table. There is no straight workaround for this.

The only way to do this is to generate small previews for each picture and store them in DB as OLE bitmaps. Then you display em with "Bound Object Frame"

Its hard to code such a trick by your own - but you can try AccessImagine ActiveX control, it does a trick easily. Beside that it allows to put images to database in one click - load, paste, scan or drop.

 

[SOS]

Unfortunately earlier versions of Access weren't adept at this. But, Access 2007, believe it or not, has the ability to bind an image control to a recordsource (hence file path) so it does work on a continuous form. (another selling point for the 2007 version)

 

[Max D]

Hm, i havn't got the whole plot. There is several control types and several problems

Bound Object Frame - need an OLE object written to database, works with continuous forms. [Problem - OLE object size = uncompressed bitmap size]

Attachment - writes files to database, works with continuous forms. [Problem - not eligable field type for SQL server and other ADP-type projects]

Image - can handle graphic files inside and outside database, needs a little VB-coding [Problem - doesn't works with continuous forms]

It makes me laugh sometimes, to be honest. Does "Bound Object Frame" works on continuous forms in pre-2007 versions of Access?

 

[SOS]

Does "Bound Object Frame" works on continuous forms in pre-2007 versions of Access?

Not that I'm aware of. The image would need to be stored IN Access as an OLE type (which of course bloats the database in any version prior to 2007).

In 2007 the IMAGE (your third option shown) now has the control source that can be bound to a path.

 

[Max D]

Yep, my fault. IMAGE really works. Doesn't it bloat computer resources when displaying a table with lot of big images?

 

[SOS]

Yep, my fault. IMAGE really works. Doesn't it bloat computer resources when displaying a table with lot of big images?

when using a file path for an image control the files are stored OUTSIDE of the database, so no database size change. You can still store them in Access but there really isn't an advantage that I know of to do so.