A family of Microsoft relational database management systems designed for ease of use.
Maybe one of those references had a GetUserInfo function, and we can see how that would cause ambiguity.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have a macro that worked wonderful in MS Access 2010. Our department upgraded to Office365 and now I continuously have issues with it. I am getting this error message when running my Macro to update the DB.
It stops on the RunCode; Function Name GetUserInfo(). The purpose of this macro is to run other macros that connect to an Oracle DB on the server to return the agency cases received counts and input them into the table.
I've tried everything I have researched on the internet and nothing has worked. These are the references that are checked:
Can someone help me please? This database is used to track our agency data submissions. I'm not an expert in VB.
Thank you in advance.
A family of Microsoft relational database management systems designed for ease of use.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Maybe one of those references had a GetUserInfo function, and we can see how that would cause ambiguity.
All of a sudden, the macros are working. I made some changes to References and changed them back and now it is all working. I don't get it.
I am going to try and create a new blank DB using the MS Access 2016 version we have now and import all of the DB tables, queries, form, macros, modules, etc.
Thank you.
That suggests there is another object named GetUserInfo. Open any module and undertake a 'find' (Ctrl+F) on GetUserInfo for the current project.
Do you get the same error if you enter ? GetUserInfor in the immediate window (Ctrl+G)?
Yes, it stops at the GetUserInfo () Run Code. That is when I receive the error message "The expression contains an ambiguous name. Verify that each name in the expression refers to a unique object."