Image control and pcitures (2000 SR-1)

Topic

New Reply

I’ve just had a browse through the forum for posts about the use of an image control (instead of an OLE object) to display pictures.

I’m using the line below attached to both the On_Current event for a form and the On_Format event for the detail of a report:

Me![MyImage].Picture = Me![Image Path]

where ‘MyImage’ is the image control and ‘ImagePath’ is a textbox where the path is stored

When I use the record navigation buttons to move between records on the form the mouse pointer seems to be attracted to the image control – i.e it is dragged away from the ‘next record’ button.

Additionally, when the report is opened the screen appears to flicker as a number of dialogs appear and then disappear. I think this is each image loading but its all a bit quick.

Is there any way I can get around both these issues?

Reply | Quote

Replies

I can’t help you with your first question – I haven’t experienced such behaviour.
For the second one, see API: Suppress the “Loading Image” dialog on Dev Ashish’s Access Web.

Reply | Quote

I use this way also for my images.
Just tested to see if I get the same issue and mine seems ok.

See attached it may help you.

You’ll need some images in a folder C:home for this to work and set references to DAO 3.6.

Hope it helps you.

Reply | Quote

I use this way also for my images.
Just tested to see if I get the same issue and mine seems ok.

See attached it may help you.

You’ll need some images in a folder C:home for this to work and set references to DAO 3.6.
As you mentioned about the screen flickering and dialogs popping up, Yes, this is the images loading.

I prefer to see the image progress loading dialogs, the user can see something happening as they watch the screen.

Hope it helps you.

Reply | Quote

There’s a sample database attached to this post that demonstrates using an image control with navigation buttons, and it doesn’t change the mouse cursor’s position.

Reply | Quote

Firstly, thanks everyone for the prompt ideas.

Charlotte, I’d found your sample database before and it also behaves a bit oddly on my pc, except on the record with a bitmap of the yahoo logo.

So, I’ve just replaced the jpeg images I’m using with bitmaps and, guess what, yep, my database behaves fine – no mouse pointer skipping about. Now I’m really confused but I guess I can live with it – unless anyone has any others ideas that is.

Now to try to suppress the loading image dialogs

Reply | Quote

“Loading image dialogs”? Those much be very large images or you have a very slow machine. I don’t think I’ve ever seen a loading image message. Oh, wait. Are your images living on a network drive?

Reply | Quote

Current all the files are accessed locally, my pc isn’t particularly slow (256MB RAM, 1GHZ processor) and the images aren’t large (3kb jpgs or 90kb bitmaps). There are only 10 records but I definitely see a fleeting glance of each dialog as the report – showing all records – opens.

If this was used for real, the files probably would be accessed across a network so I’m not sure how successful it will be.

However, I’m just testing the water with this idea at the moment – you may remember some very old posts I made about databases with OLE objects where we ended up with a monster db (only 200 records but nearly 500 MB in size).

Anything has to be better than that!

Reply | Quote

You might try putting in an Application.Echo False before the line setting the picture property and then an Application.Echo True after it. Just make sure your error handlers also turn the echo back on or you can get stuck with an invisible dialog waiting for a response in the event of an error.

Reply | Quote

With your report I would use the On Print event to do the .Picture property assignment. I recently developed an app where I am printing images and have found that this cuts down considerably on the flickering and it also improves performance.
Incidentally, has anybody had problems creating a snapshot file from a report containing images? I have found when my images (.jpg files predominantly) are larger than a certain size, roughly 60-64K, then the OutputTo snapshot format sometimes fails. Also, this happens with multiple, smaller image files that appear on the same page in the report. The failure happens when I’m using Access 97 but doesn’t using Access 2000. Unfortunately, my users are running 97 with no upgrade plans in the works.

Reply | Quote