Using the Date field as a key in the Summary, going across not down, should help you out.
Aha - ouch - no. Just read your post again. Sorry, it won't work in one pass. You'll need a different approach, reading in the entire data set, and exporting a fresh summary each day.
And what happens after eighteen months or so when you have more than 512 fields going across and go beyond the limits of local SQL?
Thanks for the reply.
I think that will work, the data I have has the date in every column already. I just set up the model and will have to eventually test through Automator and such but I put the date for a key field across and got rid of the across total and it looks good. I will get that summary then use DPS to append the data by adding the column.
I knew eventually the amount of columns would become an issue but if I cut it off to a new table every year I think that would work, then just a manual copy and paste to a master file.
Olly thanks a bunch for your knowledge and help,