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. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at email@example.com and provide your corporate email address, company, and name.
I have SET ALL = PASS at the beginning of my fex. Towards the bottom I try to join a list of 8 IDs back to my main master file. For some reason, my fex eliminates those IDs in the master file that are not in the list of 8. How can I prevent this from happening? I want the finished masterfile to contain all IDs, not just the 8 that are in the short list. I thought SET ALL = PASS prevented this from happening.
You could try turning your join around - list your main master file first and your list of 8 second. However, from your post, it sounds like the ID's you have in your list of 8 are not in the main master file at all. In that case, a join will not work regardless of which file is listed first and Susannah is correct - MATCH is your only option. JOIN is for linking up 'like' records between a 'parent' and a 'child' file. If you have records in the 'parent' file that are not in the 'child' file, then SET ALL = PASS will make sure do not lose them. One thing to note, for 'parents' without 'children', the values in all their associated 'child' fields will be null, because they don't have any 'children'. So if you do any filtering against fields in the 'child' file, you will still lose your parents even with SET ALL = PASS unless you include nulls in the filtering.
Data Migrator 5.3, 7.1, 7.6 WebFOCUS 7.1, 7.6, 7.7 SQL Server, Oracle, DB2 Windows
Do you mean you want a work around for: TABLE FILE CAR PRINT TRUCK END ..which would produce an choking error. yikes. if i had to, i would do my join first, then CHECK FILE mastername HOLD then TABLE FILE HOLD and read the field that contains all the fieldnames for that joined entity, producing some nice little list. Then make sure your report uses only the fieldnames in that list. If i had to..
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
Yeah, something like that. This fex will run on a schedule every day. I have an ACROSS in my fex that turns measurements into fields. Some days, some of those measurements will be there, some days they won't. So, after that, when I want to print out specific measurements, if one or two are missing, I still want the others to print out.