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 like to be a good programmer citizen, and that means issuing my SQL*Server requests with a nolock. Is there a way to do this in native FOCUS code?This message has been edited. Last edited by: FP Mod Chuck,
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007
NOLOCK Is equivalent to READUNCOMMITTED. So, you would use the RU option.
Yikes! So if I set using that command I can issue a TABLE FILE request and it will adhere to the restriction, yes? I should put SQL SQLMSS SET ISOLATION RU; at the beginning of the focexec to achieve the result? The documentation isn't very clear on that.
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007