DLL error when importing Excel file to Access 2016

Question

I have a user (userA) trying to import an Excel file into a new Access database.  He is taking the route displayed in the below screenshots, and gets the same 'Cannot find DLL entry point GetUserDefaultLCID in kernel32' error message each time. 

A different user (userB) on another PC who is able to import the Excel file into an Access database.  I have mirrored the programs installed on userA's with userB the best I could, and still no luck.  I have tried saving the Excel file as different file types and importing it that way, but issue persists.  I have also tried installing Office 2013 x86, Office 2013 x64, Office 2016 x86, and Office 2016 x64; however, the issue persists.

UserA:

Windows 10 x64 Enterprise

(He previously had a different computer with Windows 7 x64 Enterprise, and was still unable to perform this action on that machine.)

UserB

Windows 7 x64 Enterprise

Answer 1

GetUserDefaultLCID is a Windows API call. Are you using that somewhere, or does the Excel file you're trying to import use that?

If so, then check the code to be sure it works as expected.

If not, then I'd suspect you have troubles with your installation of Office or Windows. Be sure they are both up to date, and try restarting your machine.

Answer 2

GetUserDefaultLCID is a Windows API call. Are you using that somewhere, or does the Excel file you're trying to import use that?

If so, then check the code to be sure it works as expected.

If not, then I'd suspect you have troubles with your installation of Office or Windows. Be sure they are both up to date, and try restarting your machine.

No other file is using that Windows API call.  I have even tried creating a brand new spreadsheet with a few rows and columns, and I get the exact same error message when attempting to import that.

I have uninstalled/reinstalled Microsoft Office 2013 x86 and x64, Microsoft Office 2016 x86 and x64, but still get the same message.

Answer 3

While waiting for more suggestions from other members of our community, you can also post this query on TechNet so that our experts will be able to provide you with alternative steps which can help to identify the correct solution.

Regards.

Answer 4

You cannot run Office x86 and Office x64 on the same machine so I assume that is a typo.

If it works on MachineA but on on MachineB, then the cause is environmental. Either your installation of Office or Windows is corrupt, or needs to be updated, or you have issues with the installation of your application.

Does your application use any non-native references? If so, then you must be sure those references are available on the target machine. Access won't do this automatically (nor will any other programming environment, for that matter) so you must be sure of this.

Answer 5

Scott, the OP is not stating they've installed x86 and x64 versions simultaneously. The OP is simply stating they've tried all versions of Office - x86 and x64 - at different times and regardless of which version they use, they have the same issue.