By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,953 Members | 1,161 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,953 IT Pros & Developers. It's quick & easy.

Switch function max number of varexpressions in Access xp

P: n/a
jr
I have a niggle with the Switch function

I have a querey which has a column with 3 digit values of which there are
about 20 which are unique.

These are meaningless to the user and so using the switch function I assign
a string to each value.

theus
alias
Field4: Switch([fieldx2]=210,[field3]="government
Stock",[fieldx2]=209,[field3]=""equity",etc etc

However it seems I can only have up to about 15 conditions and I need abot
22

Does anyone know if there are settings to increase this

Or an alternative without me haveing to creater the values in a table and
linking it with my query - Although if else fails that is what I will do.

john rutherford

Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
On Sun, 12 Jun 2005 11:23:03 GMT, "jr" <jr************@virgin.net> wrote:
I have a niggle with the Switch function

I have a querey which has a column with 3 digit values of which there are
about 20 which are unique.

These are meaningless to the user and so using the switch function I assign
a string to each value.

theus
alias
Field4: Switch([fieldx2]=210,[field3]="government
Stock",[fieldx2]=209,[field3]=""equity",etc etc

However it seems I can only have up to about 15 conditions and I need abot
22

Does anyone know if there are settings to increase this

Or an alternative without me haveing to creater the values in a table and
linking it with my query - Although if else fails that is what I will do.

john rutherford


If you are using a Switch statement to convert numbers to names, the question
I have to ask is - why don't you just have a table of items with numeric IDs
and text names, and join to the table the get the names?

I notice you thought of that, so why are you avoiding going that route? That
would usually be the obvious way to do things in a database application, not
the fallback poisition you would try to avoid.
Nov 13 '05 #2

P: n/a
jr
Good question
I suppose its down to habit complexity and performance.
Introducing another table is fine but it adds to the process.
This particular query is 2nd level from sourced ODBC connected table data
which will then be grouped at a third level query - There are also four
other sets of data with 1st 2nd and 3rd grouped query data - And at summary
4th levelquery the various key business information value fields are
selected.

But at the end of the day you are right - I was only wondering if the SWITCH
settings could be adjusted either by access user - or the infamous Corporate
XP security admin and packagers The bain of all developers lives.


"Steve Jorgensen" <no****@nospam.nospam> wrote in message
news:jo********************************@4ax.com...
On Sun, 12 Jun 2005 11:23:03 GMT, "jr" <jr************@virgin.net> wrote:
I have a niggle with the Switch function

I have a querey which has a column with 3 digit values of which there areabout 20 which are unique.

These are meaningless to the user and so using the switch function I assigna string to each value.

theus
alias
Field4: Switch([fieldx2]=210,[field3]="government
Stock",[fieldx2]=209,[field3]=""equity",etc etc

However it seems I can only have up to about 15 conditions and I need abot22

Does anyone know if there are settings to increase this

Or an alternative without me haveing to creater the values in a table andlinking it with my query - Although if else fails that is what I will do.

john rutherford
If you are using a Switch statement to convert numbers to names, the

question I have to ask is - why don't you just have a table of items with numeric IDs and text names, and join to the table the get the names?

I notice you thought of that, so why are you avoiding going that route? That would usually be the obvious way to do things in a database application, not the fallback poisition you would try to avoid.

Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.