Crystal Reports case sentitive on Remotes

[Kari]

Hi all-

Anybody out there writing Crystal reports? We have one that should
pull back opportunities by the Description. Unfortunately the opps are
entered by different people who use different cases. The report works
fine on the main SQL database but will only pull back exact matches
casewise on the remotes. We do not want to uppercase everything before
the report searches because then it will have to return all
opportunities and on some remotes this would take unbearably long.
Thanks for any help!
Kari

Sent via Deja.com http://www.deja.com/
Before you buy.

[corey_h...@my-deja.com]

Just a guess but did you first create your Crystal Reports on a
Interbase DB? SalesLogix recommends do so when working with Crystal.

Don't ask why!

Corey

In article <8uced2$8th$1...@nnrp1.deja.com>,

[dan4t...@my-deja.com]

> Don't ask why!

I'd guess that's because IB speaks a smaller subset of SQL than MSSQL7.

Kari, sounds like you'll have to pound through the descriptions.
upper()=upper() is not optimizer-friendly.

I was told by a (knowledgeable) integrator when I started with SLX that
if you don't get the categories and regardings right, reporting becomes
a nightmare...

If you can possibly restrict to some reasonable subset of either you'll
have a more scaleable query. I know that's not much, but it's
something.

-D4P

In article <8uphhf$dnl$1...@nnrp1.deja.com>,

[Kari]

Thanks for the answers. We did create the report on the Interbase DB.
I think at this point we are either going to have to actually upper
case all the descriptions or go through and make sure the cases are all
the same for like opportunities.
Kari

In article <8uslnl$14c$1...@nnrp1.deja.com>,

[mea...@my-deja.com]

If you are really having problems with the performance and need to fix
it, you could always add a field to the production table to hold the
uppercase versions of the descriptions and update it with a trigger.
The overhead sucks, but it is a usable solution when you get stuck
dealing with a case sensitive system.

If you are not concerned with the way the descriptions look, or you
don't ever display them to the client, you could uppercase them in your
main database when they are entered.

You could also propercase them when they are entered, or use a picklist
to eliminate the user mistypes.
We actually use the name of the most expensive item on the opportunity
as the description, so I don't let users touch it.

Since you are using it for reporting, you must want the descriptions
somewhat uniform so using a picklist and limiting users is probably the
best way to go.

The more options and flexibility you give to users, the more they will
screw up your data.