RE: ODBC Connection/Query

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Chris (Chris_at_discussions.microsoft.com)
Date: 01/05/05 

Date: Wed, 5 Jan 2005 11:43:05 -0800

Is it possible that your ODBC connection timed out in your query? In query
Properties, check what ODBC Timeout is set to. Changing it to 0. Will
prevent the timeout.

"Meredith" wrote:

> Please forgive my ignorance if I say any of this wrong... I was in the wrong
> place at the wrong time and managed to get myself in over my head in
> programming this database. My front end is working great, but there are so
> many obstacles on the backend, I feel like I'm drowning.
>
> I am using linked tables (which I have no control over) through an ODBC
> connection. I cannot even find the person that has any knowledge or control
> over these tables, so I have to use them as is. Trying to find the most
> efficient way to get the information from their place to mine. Using the
> tables directly isn't an option because the connection is incredibly slow. I
> figured replicating the tables locally with append query would work, but when
> I run the query on these tables I get "ODBC Connection Failed". I can open
> the tables with no problem, the first time I enter my login/password and
> voila, open table. Thought maybe I had to connect once to a table to enter
> password would work, but no. Even after entering my login/password I cannot
> go back and run the query, still get "ODBC Connection Failed".
>
> My problem in a nutshell is that I don't know the best way to get this
> linked data, which I have no control over, to a place that I can utilize it
> efficiently. I have to run updates on this data daily. I can run these
> updates overnight, which is what I'm trying to do by using queries that are
> run from a macro. The problem now is that if I can't be sure the queries
> will work, this method isn't an option.
>
> I'm open to any suggestions to make it work. If I'm going about this wrong,
> please tell me.

Relevant Pages

  • Re: MS Access looks for .mdb rather than Progress schema
    ... # Same query previously worked in Progress 8.x using SQL89. ... This entry allows you to keep your existing code written with the ODBC ... BTW, if you put all of the connect information into the connect string, ... I also tried putting the whole thing in the connection string: ...
    (microsoft.public.access.modulesdaovba)
  • Re: OpenDataSource & stored procedure
    ... recognises the ODBC escape syntax. ... You shouldn't need the connection parameter since Word gets it from the ... return multiple result sets - enough to confuse software such as MS Query ... >>> The call works in MSQuery but won't return the data to Word. ...
    (microsoft.public.word.mailmerge.fields)
  • Re: MS Access looks for .mdb rather than Progress schema
    ... This is not passthrough query sql. ... and should be translated into ODBC SQL. ... BTW, if you put all of the connect information into the connect string, ... I also tried putting the whole thing in the connection string: ...
    (microsoft.public.access.modulesdaovba)
  • Re: Word 2000/2002 - Proper Mail Merge steps for ODBC?
    ... I was able to find the MS Query button and locate my ... in both is ODBC. ... >> be certain that I am using the OLEDB method? ... >from the list of possible connection options. ...
    (microsoft.public.word.mailmerge.fields)
  • Re: Ada DB bindings and APQ
    ... >>I didn't like the use of handles for database objects. ... > will ensure that the connection will not go away until at least one query ... > things which can be made with a connection. ... That is different to ODBC. ...
    (comp.lang.ada)