Max Columns/Fields in a Query

[eepok]

Could anyone tell me if there's a hardcoded maximum number of fields/columns in a query?

I ask, because through some experimentation and the urging of others on the boards, I've finally taken a look at the SQL view of a database and found it rather easy to understand. There, I found I had more flexibility filtering a Query via SQL in comparison to the query design window. (unlimited "Or" vs. 8).

So, even though there's a definite number of columns in the Query Design window, can I ignore than and just enter what I need in the SQL view?

 

[eepok]

As per my reputation, I asked the question, got brave, tried out an assumption, and found the answer.

No, there is no limit to the number of columns in a query if you use SQL. However, at least in 2003, there is a limit to the number of query columns you can use/expand to in design view.

 

[KeithG]

I believe you can only have 256 columns in a query. Have you successfully exceed this number?

 

[eepok]

I believe you can only have 256 columns in a query. Have you successfully exceed this number?

I think I would stab myself in the eye with a knife if I ever made it to 256 columns in a query considering I'm not getting paid big bucks for my databasing.

I think I'm at 39 and only because it's easier for me to create expressions by first creating sub-expressions.

 

[RuralGuy]

You might go to Access Help (not VBA Help) and key in "specifications" to the Answer Wizard to see what is covered.

 

[KeithG]

I know there a limit because I was working on a pass through query earlier today connecting to a DB2 database and got an error saying I had to many fields defined. But if there are more than 256 fields in a table there probably is a normalization problem.

 

[Rabbie]

I know there a limit because I was working on a pass through query earlier today connecting to a DB2 database and got an error saying I had to many fields defined. But if there are more than 256 fields in a table there probably is a normalization problem.

How many fields have got defined. Was you error generated by Access or DB2