Here are work we use DSN Files to connect to SQL back-ends.
We have just moved up to SQL 2008, and I am having problems using the File DSN type "SQL Server Native Client 10.0". I can connect to the database, with god rights, but if I log on as a regular user and use Edit rights, I am not able to view the data in the SQL tables.
Where as if I use the old reliable "SQL Server" File DSN, I am able to open the tables just fine using the regular user account.
Is there an advantage to the "SQL Server Native Client 10.0" v. the "SQL Server" File DSN type?
If not, I will stick with the "SQL Server" File DSN type. I am only needing to connect to the tables, it isn't like I am trying to run stored procedures or any jobs from the MS Access front-end.
If you have any information, let me know.
Thank you,
T.J.
We have just moved up to SQL 2008, and I am having problems using the File DSN type "SQL Server Native Client 10.0". I can connect to the database, with god rights, but if I log on as a regular user and use Edit rights, I am not able to view the data in the SQL tables.
Where as if I use the old reliable "SQL Server" File DSN, I am able to open the tables just fine using the regular user account.
Is there an advantage to the "SQL Server Native Client 10.0" v. the "SQL Server" File DSN type?
If not, I will stick with the "SQL Server" File DSN type. I am only needing to connect to the tables, it isn't like I am trying to run stored procedures or any jobs from the MS Access front-end.
If you have any information, let me know.
Thank you,
T.J.
