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.
Executing the following code against a FOCUS database (SUFFIX=FOC) -- no errors
SET XFOCUS=ON
CREATE FILE FLKUPMST MODIFY FILE FLKUPMST FREEFORM LKUPKEY LKUPDATE MATCH LKUPKEY ON NOMATCH INCLUDE ON MATCH REJECT DATA LKUPKEY=ABS, LKUPDATE= 1601,$ END
CREATE FILE FMST MODIFY FILE FMST FREEFORM PKKEY LKUPKEY MATCH PKKEY ON MATCH REJECT ON NOMATCH INCLUDE DATA PKKEY=00001CAD, LKUPKEY=ABS,$ END
TABLE FILE FMST PRINT PKKEY LKUPKEY ON TABLE HOLD END
MODIFY FILE FMST FIXFORM ON HOLD FROM HOLD
COMPUTE TESTCONT = LOOKUP(LKUPDATE);
MATCH PKKEY ON MATCH TYPE " ON NOMATCH REJECT DATA END
When I change the SUFFIX to XFOCUS in the master and execute the above focexec I get the following error:
ERROR AT OR NEAR LINE 31 IN PROCEDURE LU FOCEXEC (FOC449) THE LOOKUP OR FIND FIELD IS NOT INDEXED (FIELDTYPE=I): LKUPKEY BYPASSING TO END OF COMMAND
Has anyone ever come across this error against an XFOCUS database?
Regards,
IBI Tech support has reported that this is a known issue with 7.3.5 corrected in 7.3.10This message has been edited. Last edited by: A Ceccucci,