Archives of the TeradataForum
Message Posted: Thu, 12 Feb 2004 @ 16:22:47 GMT
Subj: | | Re: DBC.AccessLog |
|
From: | | Terry Stover |
MS Access can be really inefficient at optimizing queries across the network and you can get unpredictable results with odbc and linked
tables.
I always use dynamic sql to load a passthrough query whenever I'm hitting a remote database. If you are downloading data to access then put
the passthrough query as the source table in an access make table or append query. The passthrough sql natively executes on the remote database
so the dbql / accesslog
Here's a vba code fragment, once you have the sql loaded in the querydef you can treat it like a regular attached table.
Dim sqlstr as string
sqlstr = "select * from mydb.mytable where mycolumn in (" + InList + ")"
Set qdf = db.querydefs("teradata_pt")
qdf.sql = sqlstr
qdf.Close
|