Column heading string in crosstab query not displaying entirely 1

[alexisb]

Hi. I am creating a column heading in a crosstab query as follows: ColHead: [Question]

I can see the resulting column heading but not the entire string. For example, if [Question] is "Do you have any upcoming initiatives in store for the end of 2005, early 2006?", I only see "Do you have any upcoming initiatives in store for the end of 200". The value in [Question] is based on a value in a memo field and is generated in the select query that feeds the crosstab query I am working on.

If I do a select query with a field that has a Caption entered in the table, I can see way more than 65 characters as the column heading so I'm not sure why the crosstab query is not displaying the entire text for the heading.

I have searched through this forum and couldn't find any threads with this issue. Any ideas?

Thanks,
Alexis

 

[dhookom]

I believe 64 characters is the limit for field/column names. The survey application that I created has a field in the questions table for a shorter question.

Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]

 

[alexisb]

Duane,
Thanks for your response. I originally thought that was a limit as well. However, when I tested by just creating a field in a table and entering the Caption as, for example, "1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890", all 100 characters displayed as the column name when I created a select query using that field in the table. In this case, the column heading was well over 64 characters. I don't need the field name to be large, just the value that displays as the column heading in the crosstab query, just as I got it to work for the select query I described. I hope this makes sense.
Thanks,
Alexis

 

[dhookom]

You can't display more than 64 characters as the derived column heading for a crosstab query. Why is that so important?

I never use caption properties of fields/columns so I have never run into issues.

Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]

 

[alexisb]

Thanks, Duane. That's what I was afraid of but at least now I know. I redesigned a database that contains prospects and questions/answers that previously had all data elements together in one table with the questions being part of the table structure rather than a data element. The client needs all the data output to a spreadsheet and previously a select query worked fine as it displayed the questions as the column headings using Caption from the table. In my design, I made the questions a table so they could be data rather than structure. This worked great as the client can now create and update questions without changing the table structure. However, I ran into this one problem trying to re-create the output query to Excel because now I cannot display the entire question as a column heading. For example, in the old db, "What is your name" was an actual field name in table tblProspects. I created a table called tblQuestions, in which "What is your name" is now questionID 1 and QuestionDesc is "What is your name". For the QuestionDesc values that are greater than 64 characters, the QuestionDesc value stops at 64. Except for this one issue, the crosstab query I created is exactly what I need.
Thanks,
Alexis

 

[dhookom]

Alexis,
Congratulations on choosing to normalize your table structure.

You might want to peruse my "At Your Survey" found at

http://www.rogersaccesslibrary.com/OtherLibraries.asp#Hookom,Duane.

It sounds like the table structure is similar to yours. My question table contains both long and abbreviated description/title/caption fields.

Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]

 

[alexisb]

Thanks, Duane. Someone else wrote the database and I started working on it earlier this year. I have been trying to convince the client that their database needed to be normalized for them to get the functionality they need without so much effort. I really appreciate your sharing your database with me. It does look very similar to mine. I will read it in detail and see if I can find a work-around to get the generated label to display or another way to get the logic I need to work.
Alexis