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.
Best to read chapter 9 in the manual "describing data". Page 9-3 describes Data base security. You can set up in the master all sorts of security options, including who has the right to Update.
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
I had mutiple user's updated our Focus databases that needed modify access. I added code to each process, when the Focus Databases get's opened I wtite "Y" or "N" to a flag file (like update.flg)
Then I coded a check in the other modify programs to read the flag file before update and display a message the file is being updated by another user. Of course, you have to unlock the file at the end of the update.
I know it's an old fashioned approach but it works and keeps you from getting corrupt databases.
Good Luck, Carol
Posts: 428 | Location: Springfield, MA | Registered: May 07, 2003