Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] upper vs lower case sorting

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] upper vs lower case sorting
 Login/Join
 
Pam Kratt
Platinum Member
posted
We are migrating from 533 to 765. I'm finding that the sorting is different and wondering if it's a setting I need to change. I've googled, checked the forum and my manuals, but I'm not finding it.

Before when we sorted each letter was looked at each letter as the same value regardless of whether it was upper or lower case (the ASCII value is different but that didn't matter before). Now, it sorts all upper case together and then lower case.

For example the following would be sorted in this order in 765

MICKEYMOUSE
MINNIEMOUSE
Mickeymouse
Minniemouse

Previously, I would have had something like the following:
MICKEYMOUSE
Mickeymouse
MINNIEMOUSE
Minniemouse

Is there a setting or an easy way to fix? I don't want to always have to set a fake field to sort on that I've performed the UPCASE command on.

Thanks.

This message has been edited. Last edited by: Kerry,


webfocus 8.105M; os: windows; pdf, html, exl2k, csv
 
Posts: 179 | Registered: November 10, 2004Report This Post
Darin Lee
Virtuoso
posted Hide Post
As far as I remember, case has ALWAYS mattered to FOCUS. If you do a selection on 'MICKEY' you would never get 'Mickey'. It's the same for sorting - they are not equivalent. The only way around it is to DEFINE/COMPUTE another field to sort by converting all values to either upper case (UPCASE) or lower case (LOCASE) and sorting first by that field with NOPRINT and then by the real field.

That being said, there are some DBMS's like DB2 where you can turn case sensitivity on or off. In this case, it's the DBMS, not the WF Server, that is handling the retrieval and sorting based on the SQL that is passed to it.

There may be some setting for the new version of the adapter that addresses this, but I have not seen anything about it.


Regards,

Darin


In FOCUS since 1991
WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex
Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex
WF Client: 77 on Linux w/Tomcat
 
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007Report This Post
Pam Kratt
Platinum Member
posted Hide Post
you are correct, it probably is not a change between 533 and 765. I just noticed I don't have the same scenarios (duplicates of names in varying cases) in the database that 533 is pointing to. This problem might just be appearing now and never noticed by the business before because we never had users with multiple ids before.

Thanks.


webfocus 8.105M; os: windows; pdf, html, exl2k, csv
 
Posts: 179 | Registered: November 10, 2004Report This Post
ira
Platinum Member
posted Hide Post
Pam,

DL is right on the mark (as usual). Case sensitivity always existed as far back as I can remember. UPCASE in a define/compute would be the way to go. Would be a nice NFR to have though - wouldn't it?
SET CASE SENSITIVITY = ON/{OFF}
G'luck, Ira


aix-533,websphere 5.1.1,apache-2.0,
wf 538(d), 537 (p),
==============
7.6.11 (t) aix 5312
websphere 6.1.19
apache 2.0
 
Posts: 195 | Registered: October 27, 2006Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] upper vs lower case sorting

Copyright © 1996-2020 Information Builders