Disable progressbar for Bound Image Object

[boert89]

Hi all,

I've been trying to work this out myself for the last couple of weeks - I even asked my teachers in school, but no one could help. So you're my last chance. Thanks for any help in advance.
I'm trying to include a picture in a form. The guide I've been using is from http://www.databasedev.co.uk/bound_image_form.html. So I'm storing the address of the picture in a table and I then use the OnCurrent event to set the picture property of the object.
Everything works fine, the only problem is, that whenever I load a new picture, I get a progress bar showing me how long it will take, until the picture is fully loaded. This progress bar only occurs when I'm using the school computer (Windows XP, MS Access 2003, SP 1). I don't get it at my computer at home (Windows Vista, MS Access 2002).
Is there a way to disable this progress bar generally. I don't really need it, as the pictures are small in size and so it is just a new window popping up and closing again. This confuses the user more than it helps.

Thanks for any help,
Bert

[Scott Price]

What kind of progress bar are you talking about? Is it the hourglass cursor? Doesn't sound like it...

It sounds as if you have initialized somewhere in the code the system progress meter. Have a look at this thread to see if there is somewhere in the code on the school's computer where this has been initialized and never removed.

If this is another meter like the ActiveX meter than you'll have to search through and find where that has been initialized.

If you can't find where it's initialized, try using the Application.Sys Cmd acSysCmdRemoveM eter command just before your code executes.

This next suggestion is a long shot to my mind, but if nothing else works you could give it a try, is to try the DoCmd.SetWarnin gs = False command just before your code executes. The thing I'm not sure about is if the progress meter is included in the Warnings category for Access. If you try this don't forget to set the back to True after your code executes.

Regards,
Scott

[boert89]

Hi Scott,

thank's for your answer.
I'm not talking about the hourglass cursor. This would be easy to fix. Here's a screenshot:


As I've written all the code myself, I'm pretty sure, that the system progress meter is not initialised. I've also had a look at my code and couldn't find any indication for any AcitveX meter.

The Application.Sys Cmd acSysCmdRemoveM eter command doesn't show any success and neither does disabling the warnings.

Thank's
Bert

[Scott Price]

Have a look here, especially about halfway down the article where it talks about setting text for the progress bar, if you set a one space string while the bar is displayed, the SysCmd method removes the bar... I'm still a little hazy on whether this is going to work for you, as I think they could be talking about two separate meters. Let me know if this works for you.

Regards,
Scott

[FishVal]

Hi, Bert.

The issue was succesfully solved in The BLOB (not the movie!).

Best regards,
Fish.

[boert89]

Hi all,
thank's to Fish I could finally solve my problem. The webpage that helped me getting there finally was http://www.mvps.org/access/api/api0038.htm.
Thank's,
Bert

[FishVal]

Not at all.

As for me, the solution with modifying registry key value is more reliable. But you certainly should make your own choice.

Best regards,
Fish

[boert89]

The registry key is one of the solutions suggested there.
However, I added the code to hide the progress bar, because firstly I can't be sure on which computer my database will be viewed (and marked) and I therefore can't disable the registry key there. The other problem is that I don't have administrator access and therefore can't change registry settings.
I'd suggest to try to disable the registry key, but including the code just in case the key is active and the progress bar is popping up.

[FishVal]

What I actually doesn't like in the code is that it may potentially fail in popup window identification especially if registry is modified so that progress bar does not appear. Sure the risk is minor. I guess the more reliable code should check the relevant registry key value (on app start or on form load) to bypass progress bar hiding if no progress bar is expected.

Regards,
Fish