Does a comma mean something in field criteria selection?

[pokerace]

Crystal 8.5 with an ABRA HR database. Sorry, but I don't know more than that about the specific database.

If I add a field <jobtitle> into the selection criteria and one of the manually entered job titles has a comma, crystal will give me an error and then lock up. It will list the jobs with commas if I just choose to show all available job titles, however, so I know that the job titles with a comma exists in the db.

I can't give much more info as I am helping someone else with this issue, but I was curious to know if using a comma in the criteria selection means something?

 

[synapsevampire]

You need to post what was entered into the selection criteria.

If you have no idea what is being used, then find out first, your question is vague and doesn't make sense.

Obviously there are plenty of reports running around the world that have commas in the data being returned from the database, if that's what you mean.

Saying manually entered values doesn't describe anything, wher is this entered, do you simply mean data in the database, a parameter, or?

-k

 

[Turkbear]

Hi,
Maybe ( as Synapse stated, we really need more info) this is what is happening:

You have string parameter and it is set to allow
only a single value - if you enter:

Apprentice,Electrical

for the value to use..
Crystal 'sees' this as 2 comma-separated values and, since the parameter only accepts a single discrete value, an error is thrown..
Try entering

"Apprentice,Electrical"

instead....




To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[pokerace]

So sorry. I meant to say an apostrophie. I appreciate the patience with some of my posts though

For example, if in select expert I choose the field "jobtitle" and then pick "is one of" and then type in some job titles and one of them is "Admin's Asst" then the report will lock up even though I know that "Admin's Asst" is available in the data. It only seems to happen when I use the apostrophie ' so I though that maybe it was a special character that does something else in regards to this?

 

[synapsevampire]

An apostrophe is also a single quote and might cause problems depending upon how the record selection is designed.

Instead of using the select expert, take control of this by selecting the Report->Selection formula-Record.

This shows you what the expert built, and you should consider doing the coding yourself, in lieu of using the experts, as they can cause problems.

So I'm guessing that it's constructed like this:

{table.jobtitle} is one of {?your parameter}

Which will cause problems.

I suggest that you manually edit it to use:

{table.jobtitle} = {?your parameter}

And in the future, try to manually code it, there are numerous papers written on why it doesn't do a good job.

In either case, if you post again, copy and paste what is in the record selection formula.

-k