Some clarification to the original question
Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance
Next message: Peter Downes: "UniVerse & SQL"
Date: Sat, 1 May 2004 12:04:22 -0700
The query is used to fill a CSV file that a third party
application uses to generate charts driven by the
ultimate Users. The reason I'm asking the question is to
see if there are options to speed the flow of data from
the Database to the CSV file to shorten the time it
currently takes. I can't modify the 3rd parties software
and I can't query less data so the ODBC seems like the
place to look. Your answer is logical for different
circumstances but doesn't get to the original question,
ARE there items that can be tweaked in ODBC that can
increase throughput?
Next message: Peter Downes: "UniVerse & SQL"
Relevant Pages
- SQL PassThrough - Export CSV error
... This query works perfectly (ODBC TimeOut property set to 3600 seconds). ... Now I want to execute this query and export the outcome to a CSV file via ... When running the VBA code, I get the following msg after +- 5minutes: ...
(microsoft.public.access.formscoding) - SQL PassThrough query - CSV error
... In MS Access I connect to TeraData server through ODBC. ... I've built an SQL PassThrough query that extracts the data ... Now I want to execute this query and export the outcome to a CSV file via ... When running the VBA code, I get the following msg after +- 5minutes: ...
(microsoft.public.access.formscoding) - SQL PassThrough query - CSV Error
... In MS Access I connect to TeraData server through ODBC. ... I've built an SQL PassThrough query that extracts the data ... Now I want to execute this query and export the outcome to a CSV file via ... When running the VBA code, I get the following msg after +- 5minutes: ...
(microsoft.public.access.modulesdaovba) - SQL PassThrough query - CSV error
... In MS Access I connect to TeraData server through ODBC. ... I've built an SQL PassThrough query that extracts the data ... Now I want to execute this query and export the outcome to a CSV file via ... When running the VBA code, I get the following msg after +- 5minutes: ...
(microsoft.public.access.formscoding) - 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) |
|
