PARAMETERS FISCALMO IEEESingle;
SELECT *
FROM [01-GL History Query]
WHERE ((([01-GL History Query].TYPE)=3) AND (([01-GL History Query].YRMODA)
Like "10*"))
ORDER BY [01-GL History Query].AMOUNT;

There is my query where I finally got the parameter fixed where FISCALMO
would prompt for the month. The crosstab isn't picking up the other
"explicitly" stated criteria. For the FISCALMO to work I had to remove the
parameter from the criteria pane in the query "designer" and declare it in
the "Parameters" section from the menu bar. Can a parameter be "explicitly"
stated for a crosstab? If so, how? Or do all criteria for a crosstab need
to be parameterized in the same manner as the FISCALMO?

First create a select query with the parameter defined. Name this query
something and make sure that it works as you expect. Leave off the Order By
as the crosstab won't use it anyway.

Next create a crosstab query using the name query created above as the
record source.

The SQL that you posted doesn't make sense to me as the FISCALMO parameter
isn't used in the Where clause.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


"gator" wrote:

> PARAMETERS FISCALMO IEEESingle;
> SELECT *
> FROM [01-GL History Query]
> WHERE ((([01-GL History Query].TYPE)=3) AND (([01-GL History Query].YRMODA)
> Like "10*"))
> ORDER BY [01-GL History Query].AMOUNT;
>
> There is my query where I finally got the parameter fixed where FISCALMO
> would prompt for the month. The crosstab isn't picking up the other
> "explicitly" stated criteria. For the FISCALMO to work I had to remove the
> parameter from the criteria pane in the query "designer" and declare it in
> the "Parameters" section from the menu bar. Can a parameter be "explicitly"
> stated for a crosstab? If so, how? Or do all criteria for a crosstab need
> to be parameterized in the same manner as the FISCALMO?