Need to disable Importing Dialog Box when .JPG images is loaded in MS Access Applicaiton

You can write to the registry using VBA. To do that, you'll need code something like this:

http://vba-corner.livejournal.com/3054.html

See the "Saving a Registry Key" section for a code sample. To use that code, you'd call it like this:

RegKeySave "HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\Graphics Filters\Import\JPEG\Options\ShowProgressDialog", "No"

If you intend on deploying this, users will need to have permissions to write to the hive (most would be able to write to the HKCU hive, of course).

Note also that modifying the registry can wreak havoc on the system, so it's always a good idea to make a reg backup first.

Thanks LSM, that's definately part of what I need, but before I include code to write to the registry I need to test the results on my test machine, and the problem is, I can't even figure out how to make the registry change on my test machine without code!

When I use regedit to look at the registry I only get as far as:

"HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\Graphics Filters\Import\"

Once I open the Import [folder?] there is no JPEG folder as per the instructions.  I'm not sure whether this is because I need to create one, or whether it is because my machine uses a different version of the operating system.

Should I create the folder on my test machine so I can test whether this does indeed hide the dialog box and solve my problem?  As I mentioned before, I' hessitant to mess with the registry unless someone who knows a lot more than me tells me to go ahead!

Thanks!

Yes, you'd need to create the keys/subkeys as needed. So you'd first create a subkey names "JPEG" on the Import key, and you'd then create a subkey named "Options" on the new JPEG key you just created.

After you've created the Options key, you'd then add a String value to that key named "ShowProgressDialog" and set the value to "No".

LSM or anyone who can help!

I have not been able to stop the Importing dialog box from appearing when importing .jpg files.

I followed your instructions exactly without issue, and then rebooted the machine.  I then openned the registry and verified that the new key I created was still there, and that the value was set to No.  

Next, I started my MS Access VBA applicaiton and openned the form that includes the .jpg files one easy page.  The dialog still appears.  When I depress the NEXT button three times fast the system crashes and control returns to the operating system.

Do you have any other ideas?  Either why the registry edit does not work, or some other way to surpess those dialogs?

My application runs in Access 2K and I'm using XP Professional SP3.

Thanks

Did you also set the same key on HKey_Local_Machine? The link you provided earlier indicates you must have the reg fixes in both locations ..

Oh yes, the HKey_Local_Machine key seems to already exist in a virgin XP install.  

I am confused that the key name is JPEG an the file extention is JPG.  I realize JPEG is just another way to say JPG...

LSM... I'm surprised there's not a more well known way... These importing boxes that appear every time an image loads are VERY annoying, and they do cause applications to crash.  I've been plagued by this problem for years!  You may remember it, you tried to help me with this before at least once.  In the past when you tried to help me, we didn't realize it was a known problem caused by the importing status box.

If anyone else has any ideas, please help!  This has been a real nightmare for us!

Can anyone else help?

Yick! :-)
Moving to another version of Access is not a good choice for us at this time.
We are currently extensively using a module to send all of our emails that is not compatible with later service packs of Office 2K and later versions of Access.

Of course I can convert all of our existing email routines, and may do so soon anyway, however, the not broke don't fix strategy seems best for now.

It does seem that this is more of an Office or Windows XP issue than that of an Access issue.  Am I asking my question in the best forum?

Thanks again.

We are currently extensively using a module to send all of our emails that is not compatible with later service packs of Office 2K and later versions of Access.

Understandable, but if you decided to stick with an Access version that is 5+ versions old, you're going to have to deal with software that is no longer in support or active development, and that is NOT compatible with the operating system, etc etc.

however, the not broke don't fix strategy seems best for now.

Ummm ... it IS broke, and it seems you must fix it. As I stated previously, the problem you're having now is a known issue with Access 2000, and is fixed in later versions apparently ... so it's difficult to say that it's "not broke". I understand that your email code is "not broke" ... but that's sorta like saying "the radio works great in my car, so my car is not broke other than the transmission doesn't work and motor won't crank". Your car IS broke, but portions of it still work okay.

It does seem that this is more of an Office or Windows XP issue than that of an Access issue

Curious why you would say that. Does your program work on other versions of Windows (like Windows 7, for example), but not on Windows XP? Does it work when running other versions of Office (like Office 2003/2007/2010) but not some?

From what you've written, it seems that your database fails regardless of (a) the Office version or (b) the OS version, so I don't see how you could come to the conclusion that the issue is Office or OS related only.

Thanks again for the help.
I'm going to close this question out and then repost to see what happens.

It's clear that this is a known problem and at one time had a solution.
My guess is that one of the XP Service packs have changed something.
I say this because I can't figure why else the published fix does not work for me.

By the way, the machines we are using are all using XP SP3, and this problem has existed for years.  The guys learn to simply move slowly through the record, or use a search function I created even if the record they want is only a few records away.

The machines have little if any, other software installed.  When I compile the code using Access 2010 I get an error due to one of the Outlook references that I'm using to sent email.  If I delete the reference, all seems to work fine except the email.  I never tested to see if this problem goes away, I guess that will tell me whether I really have a good reason to upgrade to Access 2010.  I'm just scared to do so, because this software, with the exception of a few glitches, is rock solid for the most part.

Thanks for giving me the idea to try a later version of Access to see if it fixes the crashing problem!

I really don't want to upgrade at this time for multiple reasons, so I plan to relist this question.
I'm sure there is a way to turn off this filter as there once was.  Perhaps an operating system patch or some other change is required.  Thanks again.

My guess is that one of the XP Service packs have changed something.

The only way to really determine that would be to build out a bare-bones XP machine, install your software, and then install service packs one-by one to determine where it breaks.

Even then, you'd very likely lose functionality (or worse yet, expose your systems to risk) if you decide to NOT install service packs or hot fixes that come after the one that breaks your software.

That's your call, of course. Just seems to be an exercise in futility to me ...