Terry,

There are as many variations on this theme as there are people who produce
crosstab data tables. The best idea is to have a good basic routine, and
then modify it to fit the particulars of the data table or to modify your
data table to fit the particulars of the code. As you've found, you're
often better making the table change - that is why Excel doesn't accept
Cross-tabbed data as the source for pivot tables....

Glad to hear you got it working,
Bernie


"twaccess " wrote in message
...
Bernie

This works sweet as a nut !

I've left the programme as it is as I'd rather be able to use it on any
cross-tab report without having to worry about merged cells above the
headers etc..

This particular one is probably the worst cross-tab I've ever seen as
it is so large that it is almost unusable even in its present state.
With your routine, I have now converted 9 of these cross-tabs into
databases from which I'll do my pivot table reports etc..

As a point of interest, if you wanted to finesse this programme, you
could add a feature where you prompt the user to select the top left
corner of the crosstab and then use vb to crawl along the header and
row fields to determine the overall size of the crosstab without having
the user to select the whole crosstab first. But, I'm very happy with
this programme as it stands and it now has a permanent place in my
toolbox. (Hmmm, actually on second thoughts, this could tend to include
formulas at the bottom which we dont want to do, so probably best to
leave it as it is)


Thanks and Regards


---
Message posted from http://www.ExcelForum.com/