Access /SQL Calls Regedit - how to bypass UAC

We are moving our platform to Windows 7 from XP.  We have many MS Access applications that use SQL for the backend.  Built into these applications are processes for writing new ODBC DSNs to the registry.  These writes are to the key HKEY_CURRENT_USER\Software\ODBC\ODBC.INI.  Corporate policies dictate that I do not use the Current Machine key.  Users are setup as power users no admin privileges.

The shortcuts have the full path to the MDB, no MSAccess.exe in the command line.

What can be done to bypass the UAC pop-up?  How can we elevate the opening of an MDB?
Who is Participating?
Jim Dettman (Microsoft MVP/ EE MVE)Connect With a Mentor PresidentCommented:
Consider going to a DNS less setup:

  Much cleaner and simpler to avoid them.   This assumes that the users don't need access to the data from outside your Access up.

OHISAuthor Commented:
I will have to modify the code before testing; I have as many as 5 SQL Databases in various applications.  Will follow up when I have tested.
OHISAuthor Commented:
I haven't completely resolved the multiple Database issue but the code works (commenting out the attributes line as you suggested).

Good fix.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.