However, you are very likely running the x32 bit version of Access. The one (launched by default) is the 圆4 bit one. Ok, there are two ODBC configuration panels on windows. If you change the FILE dsn, then you have to re-link. However, this also means that changes to the FILEĭSN are ignored once the table link has been created. This is good since you can then distribute the application without having to ALSO copy the file DSN created. So running access as admin will up your rights to save the file DSN into the "data sources" folder, but you can also “browse” to say some folder in my documents and that also avoids the rights error/issue.Īnother TIP: Remember, All Access links with a FILE dsn are converted into a DSN-less connection. If the MySQL driver installer worked correctly, then as per the other thread screen shot (Edwards), you should see the MySQL driver as a choice.
I also suggest you always launch the ODBC manager from inside of Access as it will thus “choose” the correct manager (x32 or 圆4) for you automatic. (So either of above should avoid the rights issue). You can fix the above by exiting access, and then right click on the access shortcut and choose “run as administrator”.Īnother way is when you use “new” for the file data source and choose the driver, then BEFORE you type in the name, use the “browse” button to say some folder in my docuemnts. If you attempt to create a file DSN, you do get a message about admin rights because the “default” location for the DSN’s is located in a folder that requires admin rights. Actually, the “admin” message is often somewhat misleading.
0 kommentar(er)
