Access 2010 - DAO runtime error 3170 Could not find installable ISAM

I have Office 2010 Professional installed on two Machines. The first machine is on a Windows 7 Pro IS, and the second is on Windows 8 Pro. On the Win7, I previously had three versions running at one time, i.e. 2003, 2007, and 2010. Up until July or so, all three ran fine. I say ran fine as it applies to any code that is applicable to DAO and ADO, in either Access or Excel. Sometime around July or so, I began to receive the Subject Error Message. I tried all my might to repair the problem, you name it, i did it. I then decided to go by a new machine, hence the Win8. I did a clean Office 2010 install, and the same problem persists.

The problem tends to be specific to the "CreateDatabase" method in DAO, while allowing me to open and work with a database. As for ADO, I get the error message that the Class is not Registered. I presume they are related. I say related in the sense that I feel the errors are more specific to the OS's and where the DLL's, OCX's, and TLB's are housed and invalid Registry pointers.

My Win7 machine at my day job has only one "Program Files" Folder. This configuration was imaged off of my old XP machine. Access 2010 runs as advertised. My two freelancing machines mentioned above both have the Program Files" and "Program Files (x86)" Folders. I believe the problem is related to the folder configurations, and maybe related to an Office Update, sometime around July or so It may have earlier, as I did not permit my machines to do automatic updates until July.

Would somebody please help me with this. It is not necessary to see my Code to know where I have went wrong. I know DAO and ADO off the top of my head. I have been writing code for 25 years. In years past, I have always been able to recover problems on my on, but this one has me at wits end. Please help.

Thank you.
 

Question Info


Last updated February 11, 2018 Views 1,098 Applies to:
Answer

Hi Gina,

 

My apology, but I finally figured out what was wrong., at least where the Win8 machine is concerned. I apparently overlooked the Language Type Argument. Next I will look at the ADO version.

 

Thank you. Even when we may think we know it and have seen it all, it is a lot of times a minor oversight.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.