"can't bind name" - in crosstab query

I have a 'select query' with one fields criteria set to look at a value on a form -
[forms]![drawings]![SiteName]   - this works fine!

When I change the query to a 'crosstab' query, then click datasheet view, I get this comment:-

can't bind name '[forms]![drawings]![SiteName]'.

How can I get this crosstab query to work?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

susannahbondAuthor Commented:
Its all the points I have
Try to do a query by code:

  Copy the SQL sentence of the cross-tab query and by code do:
  In the form that you want to see the query put a button, and in his click's event put the next code:
dim sSQL as string
sSQL = "TRANSFORM Min(Tabla1.ciudad) AS MínDeciudad " & _
                " SELECT Tabla1.ID_OBJETO " & _
                " FROM Tabla1 " & _
                 " WHERE (((Tabla1.ID_OBJETO)=" & _                                  str([forms]![drawings]![SiteName])  &" )) " & _
                " GROUP BY Tabla1.ID_OBJETO " & _
                 " PIVOT Tabla1.pais; "

  dim midb as database
  set midb = currentdb()
  dim c as querydef
  set c = midb.querydefs("C_SQL") '-- this a query wildcard
  c.sql = sSQL
  This code modify the SQL'query
  And the open a the query.
susannahbondAuthor Commented:
Thanks for your help so far

I have copied the SQL sentance into code on a button.
I get 'name not found in this collection'
and the line:- set c=midb.querydefs("C_SQL") is highlighted.
What is this query wildcard
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Yes, I don't explain all.

You must create a new query that contains "nothing" (i.e. put any table and make a "simple" query) Put the name of the  query: C_SQL, and in my code I use this query to change the SQL's property.  Instead to create a new query, ...

Is a query that use like a wildcard

PS. (There are more methods to do this, but I prefer this)

susannahbondAuthor Commented:
I have done what you suggested.  The code works.. it changes the simple select query into a crosstab query.
but i still have the same problem!
If I add the line Set RptRS = c.OpenRecordset()
I get the same error - "can't bind name"
If I run the modified query directly I still get the same error.

I'm so sorry, but the code works well.

If you want I send you my example. Send me your e-mail

  My e-mail is :  guillems@i6.com
A dirty solution: Use a temporary table that is a copy of the tableset included in your crosstab query, have a "normal" query fill it with your criteria, make the crosstab get it's data from the temp table.

  I don't agree with you, my solution works well. Because I make the query "on line" so the query don't have names like 'forms![fmr]![field]', because I change this name for his value, so this solution it works me well.

In design view of the crosstab query in the Query Grid select Query|Parameters from the menu.
Add the name Forms!Drawings!siteName as a parameter and set the data type to Text.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
guillems: I was a bit short with my comment. The colon in "A dirty solution:" was included to point out that MY suggestion was the dirty one; dirty, but easier to understand. I agree perfectly that your solution is the most elegant, in fact the same I would have used. I think perhaps Susannah has included the forms... part inside the string instead of copying your example setup.

IanHinson: The parameter version will not work, did you test it before commenting ?
Trygve: Yes. On quite a few occasions I have solved problems with name binding in crosstab queries by setting the parameters.
The SQL for the actual query in question has not been given.

it's curious, where is Susannahbond?

  What he/she said about our comments?

Ian: My test crosstab test query didn't come true when I tried the parameter solution, this is why I asked if you had tested it. Maybe I did something wrong, hmmm.
Fortunately I've usually managed to get my crosstabs working ok in the end, sometimes needing the fix I described.

The problem that occurs with parameters in crosstabs was referred to in the following KnowledgeBase article:

ACC: "Can't Bind Name '[XXX]'" Error with Crosstab Query
PSS ID Number: Q91710
Article last modified on 04-02-1997
PSS database name: ACCESS
1.0 1.1 2.0 7.0 97

The information in this article applies to:
 - Microsoft Access versions 1.0, 1.1, 2.0, 7.0, 97
Moderate: Requires basic macro, coding, and interoperability skills.
If you create a crosstab query using an implicit parameter [XXX] in a
WHERE clause (criteria), you may receive the following error message:
   In Microsoft Access 97:
      The Microsoft Jet database engine does not recognize '[XXX]' as a
      valid field name or expression.
   In earlier versions of Microsoft Access:
      Can't bind name '[XXX]'
If you use an explicit parameter, the query works as expected.
A crosstab query dynamically generates column names. Therefore, Microsoft
Access cannot tell whether [XXX] is referring to a parameter or a column
name until after the query is bound.
When you build a graph, Microsoft Access uses a crosstab to build the data
to graph. If the query is a parameter query, you have to define the
parameters explicitly, as you would have to for a normal crosstab query.
To avoid this error, define [XXX] as an explicit parameter by adding it to
the Query Parameters dialog box.
This behavior is by design.
--[remainder omitted for brevity]------------------------------------

Your crosstab that won't be fixed using this method sounds like an interesting challenge.  It might have to be split into two queries, or tackled somehow else.

susannahbondAuthor Commented:
Sorry, I only work two days a week (this week only one).  these answers look great, I will digest them and get back to you.
susannahbondAuthor Commented:
Thanks for all your help, sorry about the long delays in replying
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.