.accdb not a valid win32 application
Recently after trying to set file associations for a .accdb file ( Access 2007 / 2010 file type ) , when trying to open an .accdb file it would display the .accdb “is not a valid Win32 Application”.
When trying to right click on the file and choose “open with” and find the MSACCESS.exe executable in C:\Program Files\Microsoft Office\Office 14 ( 2010) Office12 ( 2007\ it would still display the same error message. If you opened Access up and went to file open , and find the file manually it would open the file correctly. The issue is the file associations are set in Explorer , so you have to reset the file associations, then restart explorer for them to work.
Go to Regedit and deleted the following key : HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.accdb
Then download this , and run it :
http://www.pariswells.com/upload/fixaccdbfileassoc.zip
Now go to CTRL ALT Delete , Task Manager , Find Explorer.exe under processes, End the process. Then go to File and Run and type in Explorer.exe and press enter. You should now be able to open your .accdb files. A restart would of also performed this acction
.accdb not a valid win32 application,
thanks let me try and post result
thanks alot!!! it works ^^
will this work with a db1.mdb? I’m having a similar issue trying to open a mdb file with office 2007. I keep getting “db1.mdb is not a valid Win32 Application”.
I am forever in your debt!!! Your solution worked like a charm it. We did uninstalls, reinstalls, backups, you name it…and in the end they said it had to have been something I had done like changing settings or permissions, or something. Jerks!!
So relieved to know that, one, it wasn’t my fault, and two, there are intelligent forms of life out there willing to help without chargining you an arm and a leg for it. You guys are awesome!!
I am forever in your debt!!! Your solution worked like a charm!!
I just spent the past week in IT at my school trying to solve this problem. The bozos did uninstalls, re-installs, backups, you name it…and in the end they said it had to have been something I had done like changing settings or permissions, or something. Jerks!!
So relieved to know that, one, it wasn’t my fault, and two, there are intelligent forms of life out there willing to help without charging you an arm and a leg for it. You guys are awesome!!
The information available ‘out-there’ never ceases to amaze me. To have this win32 issue, that is so debilitating and yet it appears no-one can solve, and to bump into the solution you posted that works so magnificently takes my breath away.
There really should be awards for people such as you.
Sincere thanks.