Karen Thanks for the suggestion ? with 1 minor change I used it andit?s much faster than the cursor program I had created. Instead of INTERSECTingthe 2 temp tables ? unacceptable because it created a PERMANENT table and I needed aTEMP table that could be regenerated whenever needed, as a view would be ? I justcreated the Temp structure of the final table and did a 2 table select toinsert the rows into the final table.
The fascinating thing about all this, STILL unexplained asfar as I can see, is that it?s NOT that the SELECT is too big, or has 2 manycolumns.The 2 table select works justfine.It?s that there seems to be alimit of how many SUM() expressions aSELECT can have that I?m running into, but it gives the error message about ?Rowlength excees maximum of 4.096 characters?. Does the internal table R:Base creates when you do a SELECTgenerate WIDER columns if it?s a SUM? David "David Blocker [email protected] Office: 781-344-1920 Cell: 339-206-0261" -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Friday, June 11, 2010 08:27 AM To: 'RBASE-L Mailing List' Subject: [RBASE-L] - Re: Row size exceeds 4096 bytes David: Can't remember if you ended up solving this, but I had an idea and it doesn't seem like it would be very hard: 1. Create 2 temp tables with half of the columns in each. Insert data into each of the tables, including those 4 or 5 "group by" columns you have. 2. Then just do an INTERSECT table1 WITH table2 FORMING endingtable That should give you a table with all the columns, and I don't think any of the commands would exceed the row length size. Karen
