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.
New TIBCO Community Coming Soon
In early summer, TIBCO plans to launch a new community—with a new user experience, enhanced search, and expanded capabilities for member engagement with answers and discussions! In advance of that, the current myibi community will be retired on April 30. We will continue to provide updates here on both the retirement of myibi and the new community launch.
What You Need to Know about Our New Community
We value the wealth of knowledge and engagement shared by community members and hope the new community will continue cultivating networking, knowledge sharing, and discussion.
During the transition period, from April 20th until the new community is launched this summer, myibi users should access the TIBCO WebFOCUS page to engage.
You will probably need to create a stored procedure and use MODIFY/NEXT logic to delete the records. But you will want to run the stored procedure as part of a flow in order to get a log of the results. Your delete logic might look something like this:
MODIFY FILE <filename>
NEXT <column name>
ON NEXT IF <negative of your selection criteria for deleting> GOTO TOP ;
ON NEXT DELETE
ON NONEXT GOTO EXIT
Posts: 1213 | Location: Seattle, Washington - USA | Registered: October 22, 2007
I would worry about performance with the check each record/looping approach. I think the phrase "when doing database things, use a database tool" is a good phrase to live by. I would go the DBMS SQL route. Your "parsing error" might have been just some bad SQL. Send your delete statement. Set based deleting from tables (and adding/modifying) is what DBs are made for.
------ Livin' down on the cube farm. Left, right, right.
iWay 5.6 Windows Excel, Tab-delimited, XML
Posts: 23 | Location: Minnesota | Registered: July 27, 2009