FindExecutable API call fails for ACCDB file extensions
The API call "FindExecutable: Find Exe Associated with a Registered Extension" fails on a file with the ACCDB extension. The API call does work fine with the MDB extension. Clicking on an ACCDB file in Windows Explorer does work. This is a on a new, fresh Win XP/Access 2007 install with nothing else on the system and no uninstalls, etc.
This has been confirmed by folks over in the microsoft.public.vb.general.discussion newsgroup.
Microsoft Communities - FindExecutable API call fails for ACCDB file extensions
Google Groups - FindExecutable API call fails for ACCDB file extensions
Note Mike Williams statement: "There were all sorts of strange anomalies where certain file extensions were found by FindExecutable and other file extensions were not, with (up to now) no apparent rhyme or reason behind it. "
Irony/Stupidity/Blind spot
That said ShellExecute will do what I want. I had a blind spot and forgot you could send it parameters. So I’ve spent several hours getting this API call working, or so I thought until someone hit this bug, for nothing. <sigh> Worse, I could’ve added some requested functionality to the Auto FE Updater a long time ago. <bigger sigh>
I will be issuing a new release of the Auto FE Updater in the next few days after I fix up a few other minor bugs.