February 12, 2008 at 12:26 pm
Have a database in SQL 2005 SP2.
Have an Access 2003 FE using ODBC to link to the tables.
Currently using SQL SERVER ODBC Driver rather than the Native Client Driver.
Which is normally the best driver to use?
Also, had an issue today.
Linked using Native Client to Tables that use UniqueIdentifier fields as Parent Child Links.
Queries showed No Records when Tables Linked.
BUT when changed to SQL Server Driver all OK.
It was suggested that the Native Client should be used (by someone)
but this appears only to work fully with Access 2007.
Anyone got any views or knowledge on this.
March 25, 2008 at 8:57 am
I am not a technical expert but we use the SQL Server ODBC Driver and it has worked fine for several years. If the table is to be updateable via MS Access it just needs to have a unique index in SQL server and sometimes when you link to the table in Access you have to specify the index.
March 25, 2008 at 9:03 am
Native Client supports the newer features of SQL Server 2005 and I think some of the Access 2007 stuff, but I'm not 100% sure. If the ODBC driver works, I wouldn't worry about it for now.
March 25, 2008 at 9:04 am
Debra.Tope (3/25/2008)
I am not a technical expert but we use the SQL Server ODBC Driver and it has worked fine for several years. If the table is to be updateable via MS Access it just needs to have a unique index in SQL server and sometimes when you link to the table in Access you have to specify the index.
You definitely need the unique index on the SQL Server side, Access doesn't like their absence. I will frequently not specify the index in Access in order to be sure the SQL Server link is read-only. I have it r/o in permissions, I just like to double that lock.
-----
[font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font]
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply