Long time reader, first time poster.

This will surely seem an odd request. Currently using Access 2003.

Am attempting to ascertain the location (either a path to a directory, or to some sort of .bmp/.ico/.dll/.exe/etc. library) of the default command button icons - that is to say, those shown by default in the various categories (record navigation, record operations, form operations, report operations, application, miscellaneous) using the command button wizard.

I ask this not for the purposes of linking any button image to the associated file(s), but rather in an attempt to recover the default icons that now seem lost. Please see the screenshot below for reference.

Screenshot

I've both repaired my current Access installation, and completely removed/reinstalled to no avail.

Any help would be greatly appreciated.

I am not sure if these are image files, so much as xml. Do a search on your system for .png files. It may also be embedded a la Visual Studio. In that case, you will never find them.

Of course you can always make your own buttons. It's a lot of coding, but looks much better than those fugly Access buttons. Try using FrontPage to generate some buttons. Place the standard button image and the down image on your forms, make the down image visible=False, then code the mouseover event of the top button to make it visible=false and button down visible=true, and code the form on mouse over to reset the buttons. Then put your link on the buttons down image, not the normal button image.

HTH


mmcdonal

 Thank you for your reply.

My apologies. I should have originally specified I am not seeking a workaround. While I have no issues personally creating, employing, or utilizing custom images, this issue is occuring on a client machine, and the end-user is less than savvy.

As they rely on the included images for their basic db creation and operation, I would much rather re-employ the original set (which mysteriously disappeared last week) rather than offer the above (or any) workaround that does not address the original issue.

At this point, it may simply be easier to do a complete reinstallation of the client workstation, but it was my hope that I could simply track down the missing file(s), and do a manual replacement.

Again, any solution in that direction would be very much appreciated.