Stuff a value from a report into a query?

  • Thread starter Thread starter Q
  • Start date Start date
Q

Q

I've been fighting with a query and I think I've found
the solution. I have a main report that is created with
the main sort on a number in a table called 'Sequence'.

When the report is being created, I need to grab the
actual number of the 'Sequence' and stuff it into a
query, and then the resulting query gets stuffed into the
report (as a subreport).

(The reason I'm doing this is because I'm trying to get a
crosstab query to work but the problem is there are
different Column headers in each Sequence, so when I try
to get a crosstab query to work I get ALL the instances
of the column headers, instead of those that just pertain
to that particular 'Sequence'.)

I hope this was clear... I didn't know what to search
for so if someone can point me to a resource, or tell me
what part of the help file to read, or WHATEVER. This is
the most critical thing in this databse. If I can't get
this crosstab query to work and print out I don't know
what I'm going to do...
thx!

Matt
 
Hehehe, I see you over there at Tek-Tips too...

Thanks for your response. I've responded there.

Here's my most recent post:

I'm studying what you gave me there dhookom, and the more
I look at it (and maybe I'm missing something) the more I
realize I'm going to have to create a temporary table
somehow to make this report work.

The best way to describe my situation, referencing your
database, is that you have a table of customers and there
are *special* customers. The special customers go as
column headers, and the regular customers go as the row
headers. Contained therein is information as to how the
regular customers are related to the *special* customers.

But then to make it more confusing, there are say, three
groups of *special* customers, and there are different
numbers of special customers. Your regular customers are
related to only one of the special customers.

So the crosstab reports, when you create them, are going
to have different numbers of columns because of the
differing numbers of *special* customers. Since in this
example I'm using the number of "three", there would be
three cross tab reports, each with different numbers of
columns, but the crosstab report is using information
from ONE TABLE ONLY.

I'm going to study your examples more, but on the surface
I don't believe they apply to my situation.

I think the best solution for me is to create another
table called "special customers" just for the purposes of
this report. Now I just need to figure out how to create
a table on the fly during a report. *gah* :)

Blorf, are you catching this? Does it make any sense to
you?
 
Back
Top