December 22, 2010 at 6:31 am
Hi everyone,
I have deployed a MS Access ADP file that accesses a SQL Server 2005 database.
Most users seem happy but one reports having to try several times before managing to open the file.
I don't do anything rocket science with my ADP files so I wondered whether I could get away with NOT using the MSDatashape provider but I don't have any idea how to choose the provider... and what alternatives there are.
For Production, I modify the Sql connection using the Datalink Properties window but can't see any way to choose the provider...
Two questions then
1) Has anyone any idea why one user might experience this problem?
2) If this is an answer, how could I avoid using the MSDataShape provider?
🙂
Thanks
December 23, 2010 at 11:16 am
Are you using hierarchical recordsets in SQL Server? If you are not, then there is no need for the Provider keyword of the connect string. You might find the web resource Connection Strings helpful in constructing ADO or OLE DB connection strings. Another resource is Carl Prothman's website.
Wendell
Colorful Colorado
You can't see the view if you don't climb the mountain!
December 24, 2010 at 1:05 am
No, I don't use Hierarchical recordsets but I don't have access to the connection string used by MS Access.
I can only change the server name, login and password...
December 24, 2010 at 8:07 am
I believe by default Access ADPs use the OLE DB provider, but you can change the connection string. How you do it depends on the version of Access you are using. See How to programmatically change the connection of a Microsoft Access project for details on how to change it either manually or programatically.
Wendell
Colorful Colorado
You can't see the view if you don't climb the mountain!
December 24, 2010 at 9:46 am
I'll have to give that a shot after the Christmas break
Thanks
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply