Re: Which references to use?

On Dec 8, 3:13 pm, "David W. Fenton" <XXXuse...@xxxxxxxxxxxxxxxxxxx>
wrote:
emanning <emann...@xxxxxxxx> wrote innews:abf39559-57c0-4fd7-8fb8-f6948ff41d86@xxxxxxxxxxxxxxxxxxxxxxxxxxx
:

My reason for ADO is that some of my users are having database
connection issues and I want to see if ADO works better than DAO.

I strongly doubt you'll see any difference that couldn't be
eliminated with appropriate settings for ODBC and your server.

 The
accdb they're using is an Access front-end linked to SQL Server.
This accdb has been working fine for most users except for a few
whose connections time out after a period of being idle.

I don't know where those settings are kept, but I've never
encountered such a problem. I think that if I did encounter it, I'd
be looking to find out what parameters control connection timeouts
instead of trying to switch to a completely inappropriate data
interface.

 I've researched
this problem and have made recommended setting changes to pc's and
queries and all that but a few problems still persist.  Obviously
ADO is not as dead as some would like since my Access 2007 VBA
manual devotes a detailed chapter to it.  According to the manual,
ADO may be a better solution for this type of database then DAO.
So I'm testing it out.

While it's unlikely this would be the issue here, I have to say that
I've noticed that a lot of weird ODBC/SQL Server issues with Access
turn out in the end to be DNS misconfiguration issues in disguise.
It could be that the network in question is misconfigured in some
way (DNS or otherwise) and that this is leading to the
disconnections. If that's the case, DAO vs. ADO is going to have no
effect, since the disconnects are happening at the networking layer
and not in the data access layer.

Something to look at...

--
David W. Fenton                  http://www.dfenton.com/
usenet at dfenton dot com    http://www.dfenton.com/DFA/

Thanks, David and Banana, for your replies.
.

Relevant Pages

  • Re: DAO vs ADO
    ... ADO ... > extra overhead retrieving metadata from the server for each query. ... > but I feel DAO is not as unsuitable as is often assumed. ... and ADO when working with SQL Server data. ...
    (microsoft.public.access.conversion)
  • Re: Cross Transactions between ADO & ADO.Net
    ... connection--it thrashes the server unnecessarily and discards useful server ... goes away and quietly reopen the connection when they return. ... > DTC transactions are not only heavy, they might also cause deadlocks due ... We even call ADO ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: CHANGING from DAO to RDO
    ... To boost the speed we use Terminal Server 2003 and it definetly helps on the fact that we get less corruption, but certain queries take awhile and we want to add more users. ... I don't know _where_ you got the idea that ADO and RDO were the only methods to access SQL Server. ... In fact, I have never heard of anyone using RDO with an Access database, only, in the past, with the separate VB product. ... The VB crowd abandoned it for ADO with SQL Server, even though they, too, could use DAO and, for them too, DAO was simpler and easier. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Permissions???
    ... > Server: SQL Server 2000. ... > the user could Write/Read data from server and execute stored procedures. ... > The connection was made with DSNs. ... ADO gives the following message when using stored ...
    (microsoft.public.data.ado)
  • Re: Problem with anonymous connections
    ... but you can use another user account instead-of IUSR_machine ... I'm using the ADO recordset object to get data and this is in an ASP ... the user can open a shared folder on the SSAS server first (so the user is ... > A connection cannot be made. ...
    (microsoft.public.sqlserver.olap)