|
Hi Lim. You are welcome. <snip> > > It would be really neat if somebody can somehow figure out how to make this > work for unreasonable number of feature codes. > </snip> Because you are returning a database type view, you must have one column per possible feature code, not one per potential code. I am visualizing a solution, but it would involve generating strings of data for each customer in a sub-subquery by trimming and concatenating, substringing the sub-subquery in a subquery, 10-15 levels of parentheses, and depending on the number of possible feature codes, ~300-400 lines of SQL... Before attempting this, I would try to look beyond the data in it's spreadsheet form. Who makes the spreadsheet, and what do they use to make it? Generating an uber-SQL view should be the last resort. -- "Enter any 11-digit prime number to continue..."
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.