WELL - found that this worked for me also - from REAL ECL only. And it looked hideous typing (wrapped the code around to the start.) I found that this method would NOT work from the TCL shell provided in SB+, as the "tab" entry caused the 'shell command line' to close up as if you were pressing 'enter'.
OK - good deal that this works. And it's intuitive except that it's not pretty, nor is it 'usable' from within SB+. So I have a work-around!! Hopefully the new 'command line' interface that is coming out Real Soon Now works more like SQL does will have the ability to handle this more 'neatly' than this as well. Thanks Larry! I should have read the oldest response first!! -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Larry Hiscock Sent: Tuesday, November 02, 2010 1:18 PM To: 'U2 Users List' Subject: Re: [U2] INPUTIF statement in Universe {Unclassified} I just tested ... TO DELIM " " ... (i.e. press the tab key in between the quotes) and it worked for me. UD 6.1.12 Larry Hiscock Western Computer Services -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of David Wolverton Sent: Tuesday, November 02, 2010 10:59 AM To: 'U2 Users List' Subject: Re: [U2] INPUTIF statement in Universe {Unclassified} UniData 7.1.9 --- Using list filename field-a field-b TO DELIM "|" c:\Test.txt Works and generates a "Pipe Delimited" text file... (I have to use 'lowercase LIST' so that it does work due to ECLTYPE, but that's OK) BUT -- I need the resulting file to be tab-delimited - the 'consumer' for the file is a stupid old program and cannot accept XML. It can only eat tab, or comma delimited files. And since some of the data CONTAINS commas, the TAB seems to be the better choice. Using TO DELIM "^009" will not work that I can see. And I think in this day and age, having to write a program to generate this simple of a file seems a bit over the top!! The other choice - building a dictionary called "tab" -- but I need to extract about 40 fields for this issue, so I was hoping to NOT have to build a 'hard coded' dictionary that was itself just a CHAR(9) so that my command line does not have 'tab' as every other word and get near the 'max length' along the way! That is, I didn't think I should have to do this: list CLIENT.MASTER field-a tab field-b tab field-c TO c:\test.txt I mean, tab delimited file. How routine is that?? Why would I have to build a 'fake dictionary' to handle that? Am I missing something? How do others deal with this issue? Or is the 'fake dictionary' the 'state of the art' methodology today?? _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
