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.
I am facing a problem with a scenario using the paramater variable in WHERE clause. The user selected value from HTML filter page will be passed to TABLE FILE where clause. If the parameter values has special character "$" (dollar) symbol, then it is not parsed to the table to fetch the value and ending up with an error (FOC1135) INVALID KEYWORD -* SEGNAME. T_
. For example, the Porduct table has following structure Product_Name | Product_Location Orange London AT&T USA Sports$100 UK
TABLE FILE PRODUCT
PRINT *
WHERE PRODUCT_NAME EQ 'Sports$100';
END
(FOC1135) INVALID KEYWORD -* SEGNAME. T_ORA_PRODUCT.
I have tried QUOTEDSTRING option but no luck. Please let me know if anyone have tricks to handle this.
Thanks, KarthiThis message has been edited. Last edited by: Kerry,
? 1135
(FOC1135) INVALID KEYWORD %1.%2 %3 LN %4
The keyword has not been found in the parsing table, so it is not a
documented Access File keyword for this type of Interface. Check the
spelling of the keyword and make sure the correct delimiters are
used. Make needed corrections.
Does that shed any light?
-- At least it indicates the issue (if not a red herring) lies in the synonym.
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
Focal Point Forums 