I didn't put in a character in the example as I "assumed" this was for a report, vs using as ID in another file, or exporting for a need later to parse the two apart.
If you had a mfg code (say 2-3 letters) and and part code (say 1-4 numbers) You really wouldn't need a separating character. ABC2114 Is just as easy to read if not more than ABC|2114, since | looks a lot like a 1. you could use _ for best results ABC_2114, but I gather from the request that a character wasn't needed. George >-----Original Message----- >From: Allen E. Elwood (CA) [mailto:[EMAIL PROTECTED] >Sent: Thursday, August 12, 2004 1:27 PM >To: [EMAIL PROTECTED] >Subject: RE: [U2] How do we get unique records from Universe >file(Table) > > >Hi George, > >It's always a good idea when concatenating to be sure that you put in a >character to separate the fields so that later on it's easy to >take them >back apart if necessary. Otherwise you won't know where the >mfg.no stops >and the part.no starts. > >002:MFG.NO:"|":PART.NO > >Allen E. Elwood >Senior Programmer Analyst >Direct (818) 361-5251 >Fax (818) 361-5251 >Cell (818) 359-8162 >Home (818) 361-7217 > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of George Gallen >Sent: Thursday, August 12, 2004 08:31 >To: [EMAIL PROTECTED] >Subject: RE: [U2] How do we get unique records from Universe >file(Table) > > >You can setup a DICTIONARY ITEM that concatantes both values >IE. > >ED DICT FILE MFGPARTNO > > MFGPARTNO > 001: I > 002: MFG.NO:PART.NO > 003: > 004: combo > 005: 20L > 006: S > >Assuming they are both single valued fields: > >Then > >SELECT ORDERS SAVING UNIQUE MFGPARTNO > >George >------- >u2-users mailing list >[EMAIL PROTECTED] >To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
