Trouble with building a report from a crosstab query

  • Thread starter Thread starter clamfuddle
  • Start date Start date
C

clamfuddle

I have built a crosstab query, and now I need to create a report
based on it.

However, when I use the Report Wizard, and select that query
I'm getting an empty list of fields to choose from.

I'm stumped - I'm SURE it worked a few days ago, but maybe
I've lost a step here or something.

Thanks for your time,

Bryan
 
Does your crosstab query have a criteria? Do you have Column Headings
defined in your crosstab? What happens if you first try open the crosstab?
 
Thanks, Duane -

I can open the query just fine, and it gives me the data I wish.
I created a report from a crosstab query the other day (I'm testing
various queries and reports) but today, using the wizard, I get no
list of "available fields" in the wizard.

Bryan
 
It is obviously something I'm doing wrong - I've tried 2 databases on my
system here,
and a third database on a different system.

I know I was successful Monday, but I've slept since then and can't remember
exactly
what I did then to create the report (other than I know I have always used
the "wizards"
to create the base framework for reports).

Thanks again for your time!

Bryan
 
If you are still looking for assistance, you my try answer the questions
that I asked earlier.
 
Duane -

I apologize - I thought I had answered your questions.

The crosstab query appears to work correctly, and gives me the data
I am looking for.

I have several "row headings" - agent_id, source, campaign_name,
call_result_code

I have one "column heading" - a value which represents which shift was being
worked (AM,PM,EV)

I have one "value" item - the count of call_result_codes.

And I have 2 criteria - one which uses Not Like "U*" and one which is
DatePart("y,[SALE_DATE]) = DatePart("y",[CallDateTime])

The [SALE_DATE] clause is a parameter entered at runtime, and the
[CallDateTime]
value is a field in the table.

Thanks for your time!

Bryan
 
I'm sorry. I guess you didn't understand what I meant by having column
headings defined. I would expect that your shifts are fairly static. View
the crosstab properties and enter "AM","PM","EV" into Column Headings
property.

--
Duane Hookom
MS Access MVP


clamfuddle said:
Duane -

I apologize - I thought I had answered your questions.

The crosstab query appears to work correctly, and gives me the data
I am looking for.

I have several "row headings" - agent_id, source, campaign_name,
call_result_code

I have one "column heading" - a value which represents which shift was being
worked (AM,PM,EV)

I have one "value" item - the count of call_result_codes.

And I have 2 criteria - one which uses Not Like "U*" and one which is
DatePart("y,[SALE_DATE]) = DatePart("y",[CallDateTime])

The [SALE_DATE] clause is a parameter entered at runtime, and the
[CallDateTime]
value is a field in the table.

Thanks for your time!

Bryan
Click to expand...
 
Thank you, Duane -

That appears to have done the trick!
I appreciate your patience with me,

Bryan


Duane Hookom said:
I'm sorry. I guess you didn't understand what I meant by having column
headings defined. I would expect that your shifts are fairly static. View
the crosstab properties and enter "AM","PM","EV" into Column Headings
property.

--
Duane Hookom
MS Access MVP


clamfuddle said:
Duane -

I apologize - I thought I had answered your questions.

The crosstab query appears to work correctly, and gives me the data
I am looking for.

I have several "row headings" - agent_id, source, campaign_name,
call_result_code

I have one "column heading" - a value which represents which shift was being
worked (AM,PM,EV)

I have one "value" item - the count of call_result_codes.

And I have 2 criteria - one which uses Not Like "U*" and one which is
DatePart("y,[SALE_DATE]) = DatePart("y",[CallDateTime])

The [SALE_DATE] clause is a parameter entered at runtime, and the
[CallDateTime]
value is a field in the table.

Thanks for your time!

Bryan



Duane Hookom said:
If you are still looking for assistance, you my try answer the questions
that I asked earlier.

--
Duane Hookom
Microsoft Access MVP


"clamfuddle" <vader1 at flash.net> wrote in message
It is obviously something I'm doing wrong - I've tried 2 databases
Click to expand...
Click to expand...
on
my always
used
Click to expand...
Click to expand...
 
Back
Top