Re: [U2] Suggestions for flattening Multivalues...
On 09/11/11 19:05, Steve Romanow wrote: Are any of the multivalued fields associated to each other? You would have a subtable per association, not per column. The messiness still exists, it just needs to be managed. And are you looking to export it to MySQL (or whatever), or are you planing to make it visible from U2 via ODBC or OleDB? There's a bunch of programs on PickWiki that will dump FILEs into normalised tables, based on correctly set up associations. You might find some of it useful. Cheers, Wol ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Suggestions for flattening Multivalues...
I'll have to check them out...although, in this case, I am pulling informtion from multiple files to make up one table. I developed a system that builds an image in a dynamic array of each of the flattened rows. When it builds the arrary, before writing it, it will read the image already on file based on a key. if the image is different, it writes the old image to a history file with a date/time added to the key, and then writes the new image to a changes file using the source file as an added key, as well as writing the changed image to the saved file. Basicaly, I am left with a set of files (dynamic arrays) which mimic the MySQL tables I have a changes file which only has data which has changed (or is new) to be exported to the MySQL table next time I have a history file so I can compare the changes file against, so only the fields that change are exported. I run through the changes, sorted by the source file it came from (added to the ID when written), the source file tells the export program the name of the sequential output file that holds the INSERT / UPDATE commands Once the SQL files are completed it is pushed into MySQL to do it's thing to update the MySQL database. What is good is that if the MySQL database is ever corrupted, no big deal, truncate everything, and do a full load based on the dynamic images created, as opposed to doing a partial update. But to answer the question, no, its not to be visible from U2 It works pretty good. George Gallen Senior Programmer/Analyst Accounting/Data Division ggal...@wyanokegroup.com ph:856.848.9005 Ext 220 The Wyanoke Group http://www.wyanokegroup.com From: u2-users-boun...@listserver.u2ug.org [u2-users-boun...@listserver.u2ug.org] On Behalf Of Wols Lists [antli...@youngman.org.uk] Sent: Thursday, November 10, 2011 4:54 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Suggestions for flattening Multivalues... On 09/11/11 19:05, Steve Romanow wrote: Are any of the multivalued fields associated to each other? You would have a subtable per association, not per column. The messiness still exists, it just needs to be managed. And are you looking to export it to MySQL (or whatever), or are you planing to make it visible from U2 via ODBC or OleDB? There's a bunch of programs on PickWiki that will dump FILEs into normalised tables, based on correctly set up associations. You might find some of it useful. Cheers, Wol ___ 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] Suggestions for flattening Multivalues...
I'm in the process of creating/updating a MySQL database for external applications to analyze some of the data. My initial method of dealing with a multivalued field, is to create it's own table, keyed to the master table (1:n) But this gets a little tedious if you have a bunch of multivalued fields - and creates really bulky SQL statements with all the joins. What other ways are people using to work with 1:n relationships? ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Suggestions for flattening Multivalues... [AD]
[AD]Hi George, Our 2SQL product allows you to map graphically, then automatically creates all the tables for multivalues and subvalues. This youtube video shows how we mapped the table: http://youtu.be/-blc5rE1_CM and this one shows how we used the mapped view to create SQL Server tables (or Oracle, DB2, Progress, MySQL...) http://youtu.be/aI9TcMfCRDg -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of George Gallen Sent: November-09-11 10:34 AM To: U2 Users Subject: [U2] Suggestions for flattening Multivalues... I'm in the process of creating/updating a MySQL database for external applications to analyze some of the data. My initial method of dealing with a multivalued field, is to create it's own table, keyed to the master table (1:n) But this gets a little tedious if you have a bunch of multivalued fields - and creates really bulky SQL statements with all the joins. What other ways are people using to work with 1:n relationships? ___ 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
Re: [U2] Suggestions for flattening Multivalues...
It might be worth doing some of this work with an ORM (Object Relation Mapper). Almost all higher level languages have them. Once you get things configured, the messiness of the joins is hidden behind syntactic sugar. Here is a comparison of a lot of them from wikipedia. http://en.wikipedia.org/wiki/Comparison_of_object-relational_mapping_software SQLAlchemy is a market leader for python. If you are a microsoft shop, I understand LINQ us really nice. http://en.wikipedia.org/wiki/Language_Integrated_Query#LINQ_to_SQL On Wed, Nov 9, 2011 at 1:34 PM, George Gallen ggal...@wyanokegroup.com wrote: I'm in the process of creating/updating a MySQL database for external applications to analyze some of the data. My initial method of dealing with a multivalued field, is to create it's own table, keyed to the master table (1:n) But this gets a little tedious if you have a bunch of multivalued fields - and creates really bulky SQL statements with all the joins. What other ways are people using to work with 1:n relationships? ___ 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
Re: [U2] Suggestions for flattening Multivalues...
I was looking more for ideas on how to setup the database structure to handle the 1:n other than the Sidebar tables joined to the master table. Right now, the scope of the data being moved off is fairly small, I didn't want to involve any other apps The querying app would be custom in itself (most likely php or something) Just this one file we are moving contains about 20 different multivalued fields, and it seemed a little Overkill to have to create 21 tables to contain the data in a form MySQL can handle. I guess that what Happens when you've been raised on multivalue database structure, and are forced to work with one that Does not handle it natively! -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Steve Romanow Sent: Wednesday, November 09, 2011 1:41 PM To: U2 Users List Subject: Re: [U2] Suggestions for flattening Multivalues... It might be worth doing some of this work with an ORM (Object Relation Mapper). Almost all higher level languages have them. Once you get things configured, the messiness of the joins is hidden behind syntactic sugar. Here is a comparison of a lot of them from wikipedia. http://en.wikipedia.org/wiki/Comparison_of_object-relational_mapping_software SQLAlchemy is a market leader for python. If you are a microsoft shop, I understand LINQ us really nice. http://en.wikipedia.org/wiki/Language_Integrated_Query#LINQ_to_SQL On Wed, Nov 9, 2011 at 1:34 PM, George Gallen ggal...@wyanokegroup.com wrote: I'm in the process of creating/updating a MySQL database for external applications to analyze some of the data. My initial method of dealing with a multivalued field, is to create it's own table, keyed to the master table (1:n) But this gets a little tedious if you have a bunch of multivalued fields - and creates really bulky SQL statements with all the joins. What other ways are people using to work with 1:n relationships? ___ 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
Re: [U2] Suggestions for flattening Multivalues...
Welcome to Hell! -Original Message- From: George Gallen ggal...@wyanokegroup.com To: U2 Users List u2-users@listserver.u2ug.org Sent: Wed, Nov 9, 2011 10:57 am Subject: Re: [U2] Suggestions for flattening Multivalues... I was looking more for ideas on how to setup the database structure to handle he 1:n other than the Sidebar tables joined to the master table. Right now, the scope of the data being moved off is fairly small, I didn't want o involve any other apps The querying app would be custom in itself (most likely php or something) Just this one file we are moving contains about 20 different multivalued fields, nd it seemed a little verkill to have to create 21 tables to contain the data in a form MySQL can andle. I guess that what appens when you've been raised on multivalue database structure, and are forced o work with one that oes not handle it natively! -Original Message- rom: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] n Behalf Of Steve Romanow ent: Wednesday, November 09, 2011 1:41 PM o: U2 Users List ubject: Re: [U2] Suggestions for flattening Multivalues... It might be worth doing some of this work with an ORM (Object Relation apper). Almost all higher level languages have them. Once you get hings configured, the messiness of the joins is hidden behind yntactic sugar. Here is a comparison of a lot of them from wikipedia. ttp://en.wikipedia.org/wiki/Comparison_of_object-relational_mapping_software SQLAlchemy is a market leader for python. If you are a microsoft hop, I understand LINQ us really nice. ttp://en.wikipedia.org/wiki/Language_Integrated_Query#LINQ_to_SQL On Wed, Nov 9, 2011 at 1:34 PM, George Gallen ggal...@wyanokegroup.com wrote: I'm in the process of creating/updating a MySQL database for external pplications to analyze some of the data. My initial method of dealing with a multivalued field, is to create it's own able, keyed to the master table (1:n) But this gets a little tedious if you have a bunch of multivalued fields - and reates really bulky SQL statements with all the joins. What other ways are people using to work with 1:n relationships? ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users __ 2-Users mailing list 2-us...@listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users __ 2-Users mailing list 2-us...@listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Suggestions for flattening Multivalues...
Whenever the fields are related (an association) the related fields can all make a single table. The only other thing you can do is to explode the single values to match the multivalues, but with different multivalue counts, you wind up with lots of null values. To make it really useful, I'm not aware of any other simple options. Relational databases really work best with normalized data... -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of George Gallen Sent: November-09-11 10:57 AM To: U2 Users List Subject: Re: [U2] Suggestions for flattening Multivalues... I was looking more for ideas on how to setup the database structure to handle the 1:n other than the Sidebar tables joined to the master table. Right now, the scope of the data being moved off is fairly small, I didn't want to involve any other apps The querying app would be custom in itself (most likely php or something) Just this one file we are moving contains about 20 different multivalued fields, and it seemed a little Overkill to have to create 21 tables to contain the data in a form MySQL can handle. I guess that what Happens when you've been raised on multivalue database structure, and are forced to work with one that Does not handle it natively! -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Steve Romanow Sent: Wednesday, November 09, 2011 1:41 PM To: U2 Users List Subject: Re: [U2] Suggestions for flattening Multivalues... It might be worth doing some of this work with an ORM (Object Relation Mapper). Almost all higher level languages have them. Once you get things configured, the messiness of the joins is hidden behind syntactic sugar. Here is a comparison of a lot of them from wikipedia. http://en.wikipedia.org/wiki/Comparison_of_object-relational_mapping_software SQLAlchemy is a market leader for python. If you are a microsoft shop, I understand LINQ us really nice. http://en.wikipedia.org/wiki/Language_Integrated_Query#LINQ_to_SQL On Wed, Nov 9, 2011 at 1:34 PM, George Gallen ggal...@wyanokegroup.com wrote: I'm in the process of creating/updating a MySQL database for external applications to analyze some of the data. My initial method of dealing with a multivalued field, is to create it's own table, keyed to the master table (1:n) But this gets a little tedious if you have a bunch of multivalued fields - and creates really bulky SQL statements with all the joins. What other ways are people using to work with 1:n relationships? ___ 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 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Suggestions for flattening Multivalues...
Are any of the multivalued fields associated to each other? You would have a subtable per association, not per column. The messiness still exists, it just needs to be managed. On Wed, Nov 9, 2011 at 1:57 PM, George Gallen ggal...@wyanokegroup.com wrote: I was looking more for ideas on how to setup the database structure to handle the 1:n other than the Sidebar tables joined to the master table. Right now, the scope of the data being moved off is fairly small, I didn't want to involve any other apps The querying app would be custom in itself (most likely php or something) Just this one file we are moving contains about 20 different multivalued fields, and it seemed a little Overkill to have to create 21 tables to contain the data in a form MySQL can handle. I guess that what Happens when you've been raised on multivalue database structure, and are forced to work with one that Does not handle it natively! -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Steve Romanow Sent: Wednesday, November 09, 2011 1:41 PM To: U2 Users List Subject: Re: [U2] Suggestions for flattening Multivalues... It might be worth doing some of this work with an ORM (Object Relation Mapper). Almost all higher level languages have them. Once you get things configured, the messiness of the joins is hidden behind syntactic sugar. Here is a comparison of a lot of them from wikipedia. http://en.wikipedia.org/wiki/Comparison_of_object-relational_mapping_software SQLAlchemy is a market leader for python. If you are a microsoft shop, I understand LINQ us really nice. http://en.wikipedia.org/wiki/Language_Integrated_Query#LINQ_to_SQL On Wed, Nov 9, 2011 at 1:34 PM, George Gallen ggal...@wyanokegroup.com wrote: I'm in the process of creating/updating a MySQL database for external applications to analyze some of the data. My initial method of dealing with a multivalued field, is to create it's own table, keyed to the master table (1:n) But this gets a little tedious if you have a bunch of multivalued fields - and creates really bulky SQL statements with all the joins. What other ways are people using to work with 1:n relationships? ___ 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 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Suggestions for flattening Multivalues...
For a couple of the fields, I've done this, but for most of them, there are no range of counts. Oh well. The only other method I'll use for some of the other fields is storing them with a delimiter (very Pick like) And have the application split the data, instead of splitting it in the database. George -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Robert Houben Sent: Wednesday, November 09, 2011 2:03 PM To: U2 Users List Subject: Re: [U2] Suggestions for flattening Multivalues... Whenever the fields are related (an association) the related fields can all make a single table. The only other thing you can do is to explode the single values to match the multivalues, but with different multivalue counts, you wind up with lots of null values. To make it really useful, I'm not aware of any other simple options. Relational databases really work best with normalized data... -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of George Gallen Sent: November-09-11 10:57 AM To: U2 Users List Subject: Re: [U2] Suggestions for flattening Multivalues... I was looking more for ideas on how to setup the database structure to handle the 1:n other than the Sidebar tables joined to the master table. Right now, the scope of the data being moved off is fairly small, I didn't want to involve any other apps The querying app would be custom in itself (most likely php or something) Just this one file we are moving contains about 20 different multivalued fields, and it seemed a little Overkill to have to create 21 tables to contain the data in a form MySQL can handle. I guess that what Happens when you've been raised on multivalue database structure, and are forced to work with one that Does not handle it natively! ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Suggestions for flattening Multivalues...
Thanks for mentioning that. Yes, some are - that will cut down on some of the tables. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Steve Romanow Sent: Wednesday, November 09, 2011 2:05 PM To: U2 Users List Subject: Re: [U2] Suggestions for flattening Multivalues... Are any of the multivalued fields associated to each other? You would have a subtable per association, not per column. The messiness still exists, it just needs to be managed. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Suggestions for flattening Multivalues...
Why are you using MySql if you are after free you could use Postgresql which I believe supported nested tables built in? -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- boun...@listserver.u2ug.org] On Behalf Of George Gallen Sent: Thursday, 10 November 2011 8:06 a.m. To: U2 Users List Subject: Re: [U2] Suggestions for flattening Multivalues... For a couple of the fields, I've done this, but for most of them, there are no range of counts. Oh well. The only other method I'll use for some of the other fields is storing them with a delimiter (very Pick like) And have the application split the data, instead of splitting it in the database. George -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- boun...@listserver.u2ug.org] On Behalf Of Robert Houben Sent: Wednesday, November 09, 2011 2:03 PM To: U2 Users List Subject: Re: [U2] Suggestions for flattening Multivalues... Whenever the fields are related (an association) the related fields can all make a single table. The only other thing you can do is to explode the single values to match the multivalues, but with different multivalue counts, you wind up with lots of null values. To make it really useful, I'm not aware of any other simple options. Relational databases really work best with normalized data... -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- boun...@listserver.u2ug.org] On Behalf Of George Gallen Sent: November-09-11 10:57 AM To: U2 Users List Subject: Re: [U2] Suggestions for flattening Multivalues... I was looking more for ideas on how to setup the database structure to handle the 1:n other than the Sidebar tables joined to the master table. Right now, the scope of the data being moved off is fairly small, I didn't want to involve any other apps The querying app would be custom in itself (most likely php or something) Just this one file we are moving contains about 20 different multivalued fields, and it seemed a little Overkill to have to create 21 tables to contain the data in a form MySQL can handle. I guess that what Happens when you've been raised on multivalue database structure, and are forced to work with one that Does not handle it natively! ___ 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
Re: [U2] Suggestions for flattening Multivalues...
On 11/09/11 14:05, Steve Romanow wrote: Are any of the multivalued fields associated to each other? You would have a subtable per association, not per column. This is precisely how Datatel reverse-engineered their back end from Unidata to MSSQL. -- Jeff Butera, Ph.D. Manager of ERP Systems Hampshire College jbut...@hampshire.edu 413-559-5556 ...we must choose between what is right and what is easy... Dumbledore ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Suggestions for flattening Multivalues...
It's what I'm used to using for those small projects...I didn't realize that it supported that. I'll have to look into it...minor learning curve. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Phil Walker Sent: Wednesday, November 09, 2011 2:15 PM To: U2 Users List Subject: Re: [U2] Suggestions for flattening Multivalues... Why are you using MySql if you are after free you could use Postgresql which I believe supported nested tables built in? -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- boun...@listserver.u2ug.org] On Behalf Of George Gallen Sent: Thursday, 10 November 2011 8:06 a.m. To: U2 Users List Subject: Re: [U2] Suggestions for flattening Multivalues... For a couple of the fields, I've done this, but for most of them, there are no range of counts. Oh well. The only other method I'll use for some of the other fields is storing them with a delimiter (very Pick like) And have the application split the data, instead of splitting it in the database. George -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- boun...@listserver.u2ug.org] On Behalf Of Robert Houben Sent: Wednesday, November 09, 2011 2:03 PM To: U2 Users List Subject: Re: [U2] Suggestions for flattening Multivalues... Whenever the fields are related (an association) the related fields can all make a single table. The only other thing you can do is to explode the single values to match the multivalues, but with different multivalue counts, you wind up with lots of null values. To make it really useful, I'm not aware of any other simple options. Relational databases really work best with normalized data... -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- boun...@listserver.u2ug.org] On Behalf Of George Gallen Sent: November-09-11 10:57 AM To: U2 Users List Subject: Re: [U2] Suggestions for flattening Multivalues... I was looking more for ideas on how to setup the database structure to handle the 1:n other than the Sidebar tables joined to the master table. Right now, the scope of the data being moved off is fairly small, I didn't want to involve any other apps The querying app would be custom in itself (most likely php or something) Just this one file we are moving contains about 20 different multivalued fields, and it seemed a little Overkill to have to create 21 tables to contain the data in a form MySQL can handle. I guess that what Happens when you've been raised on multivalue database structure, and are forced to work with one that Does not handle it natively! ___ 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
Re: [U2] Suggestions for flattening Multivalues...
Try MongoDB - It's a good match to a mvdbms and has drivers for most common programming environments. djm phil walker-2 wrote: Why are you using MySql if you are after free you could use Postgresql which I believe supported nested tables built in? - Learn and Do Excel and Share http://mvdbs.com http://mvdbs.com -- View this message in context: http://old.nabble.com/Suggestions-for-flattening-Multivalues...-tp32813168p32813844.html Sent from the U2 - Users mailing list archive at Nabble.com. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Suggestions for flattening Multivalues...
I have used Sleepy Mongoose to push data to mongo via curl. http://www.snailinaturtleneck.com/blog/2010/02/22/sleepy-mongoose-a-mongodb-rest-interface/ On Wed, Nov 9, 2011 at 3:07 PM, DavidJMurray (mvdbs.com) nab...@mvdbs.com wrote: Try MongoDB - It's a good match to a mvdbms and has drivers for most common programming environments. djm phil walker-2 wrote: Why are you using MySql if you are after free you could use Postgresql which I believe supported nested tables built in? - Learn and Do Excel and Share http://mvdbs.com http://mvdbs.com -- View this message in context: http://old.nabble.com/Suggestions-for-flattening-Multivalues...-tp32813168p32813844.html Sent from the U2 - Users mailing list archive at Nabble.com. ___ 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
