S
Shane O'Keeffe
Hi,
I'm hoping that somebody can help me with a problem I'm having.
I've created a basic query with parameters and I've explicitly
declared the parameters in the Query->Parameters... menu option. I've
then created a crosstab query based on the first query. Both queries
executes fine i.e. they asks for the parameters and return valid data.
However when I attempt to create a report based on the crosstab it
fails saying that I selected a query that returns no fields. Even the
Report Wizard fails. If I choose the option to create a new report in
design view, as soon as I select my crosstab query as the record
source it asks me for the parameter values from the query a number of
times in succession.
I remember doing a query of a similar type a number of years ago and I
had never came across this problem.
I'm using Access 2003 but the database is in the Access 2000 format.
The base table that the basic query is based on is a linked table from
a SQL Server database.
All ideas/help greatly appreciated.
Regards,
Shane.
I'm hoping that somebody can help me with a problem I'm having.
I've created a basic query with parameters and I've explicitly
declared the parameters in the Query->Parameters... menu option. I've
then created a crosstab query based on the first query. Both queries
executes fine i.e. they asks for the parameters and return valid data.
However when I attempt to create a report based on the crosstab it
fails saying that I selected a query that returns no fields. Even the
Report Wizard fails. If I choose the option to create a new report in
design view, as soon as I select my crosstab query as the record
source it asks me for the parameter values from the query a number of
times in succession.
I remember doing a query of a similar type a number of years ago and I
had never came across this problem.
I'm using Access 2003 but the database is in the Access 2000 format.
The base table that the basic query is based on is a linked table from
a SQL Server database.
All ideas/help greatly appreciated.
Regards,
Shane.