Glenn:
I generally save cross tab results into a temp table. That seems to make life easier going forward with queries against it. Of course you have to manage the subsequent queries' Select statements, but it is easier, for me anyway, to look at the TableDef/FieldDefs of the temp table where the cross tab now lives, as opposed to when it exists only as dynamic result set.
To: MS_Access_Professionals@yahoogroups.com
From: MS_Access_Professionals@yahoogroups.com
Date: Tue, 16 Feb 2016 11:40:54 -0500
Subject: [MS_AccessPros] Crosstab as data source for subsequent queries
hth,
Steve Conklin
To: MS_Access_Professionals@yahoogroups.com
From: MS_Access_Professionals@yahoogroups.com
Date: Tue, 16 Feb 2016 11:40:54 -0500
Subject: [MS_AccessPros] Crosstab as data source for subsequent queries
I find myself needing to work with crosstabs lately and needing to use the output of a crosstab as the data source for another query. Crosstab field names are dynamic. By that I mean that the field names in the query result depend on the data being transformed. So the field list will have differing numbers of fields from run to run. I am currently managing the output by using VBA to generate TRANSFORM SQL at runtime and then replace the SQL in a querydef. This provides me with the source for further downstream processing that is responsive to current data and user request.
Can anyone share their insight into using crosstabs especially as the source for further querying?
Glenn
__._,_.___
Posted by: Steve Conklin <stephenmconklin@hotmail.com>
Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (2) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar