The problem here isn't that you can only have a certain number of items active in a select list, but that specifying them as explicit item ids on the command line is ugly, bad and only supported up to a certain point.
Isn't this a job for QSELECT? PS. As much as I think UniData is a great toolset to work with, anyone who told you that conversion was a save and restore needs shooting. Cheers, Ken -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Marc Harbeson Sent: Friday, 30 January 2009 12:24 PM To: [email protected] Subject: RE: [U2] UniData LIMITs What about something along the lines of splitting the client ID's into two (or more) lists, selecting, and then MERGE.LIST them together then list? Kind of difficult to guess around it without seeing the whole picture. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bill Haskett Sent: Thursday, January 29, 2009 7:12 PM To: [email protected] Subject: Re: [U2] UniData LIMITs That's correct. Bill ______________________________________________________________________ From: Kevin King <[email protected]> Sent: 1/29/2009 2:37 PM To: [email protected] Subject: Re: [U2] UniData LIMITs And the client records don't share any specific attribute, like a company number or such that you could use in the selection? ------- 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/ ------- 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/
