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.
Currently i got a requirement on finding anomalies b/w two tables in two databases. Both tables represent the same type of data (Product) but there are few feilds in tables which are not common.
1.I want to write a .fex to fine the data in table A and not in table B and vice versa.
There are two common feilds "description" and "Age" in the tables which are not sortable which has to be same, so i need to compare those details too.
The solution in my mind is to merge "Table A" and "Table B" then use a where clause to compare.
if you have come across this situation please advice on a solution.
Regards G9
Posts: 18 | Location: Kochi, Kerala, India | Registered: August 26, 2008
I agree with Tony on using MATCH, but I think you should look into OLD-NOR-NEW. OLD-NOT-NEW will give you the items from the first file that are not in the second, OLD-NOR-NEW will give you the items from either file that don't match.
Pat WF 7.6.8, AIX, AS400, NT AS400 FOCUS, AIX FOCUS, Oracle, DB2, JDE, Lotus Notes
Posts: 755 | Location: TX | Registered: September 25, 2007
That's why I included the "etc." to imply that there was more to it than just OLD-NOT-NEW, thus encouraging Robing9 to go and look and determine the best method for him / her.
Keep smiling
T
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004
I use a similar process to compare old and new systems to ensure the logic written into the new system is comaprable. This requires comparison at field level so I MATCH the files together OLD-OR-NEW and then define or compute flag fields to identify which fields are not comparable. I exclude those data rows which compare in every field and then by changing the colour of the comparable fields to white and output to EXL2K I can see what the differences are quickly, but still see the underlying data values by selecting all cells as necessary.
T
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004