So I think you should change your handle. Cynthia is a really pretty name, but "IamtheSASGoddess" seems to be quite appropriate . . . lol. Really impressed with your knowledge base and thanks for the help . . .
But I'm guessing you don't know a ton about baseball. Here's a link to the zone map i was referring to.
http://www.retrosheet.org/location.htm
Essentially a ball is hit in a zone and it is either fielded for an out or it goes for a hit. Now, this can happen under a number of different situations, hence the categorical variables which i'm evaluating. So I have sorted the raw data (and filtered it; took me a LONG time) and then subsetted each event into one of the zones on the map. Then within eacch zone, i then evaluate how good the model is at identifying who is a good fielder and who isn't. To do so, i need the group data/summary stats.
So yes, an excel spreadsheet with 70 sheets would be perfect.
Ok, here's what i've got from proc tabulate.
[pre] proc tabulate data=_9S out = _9SSummary;
options missing = 0;
class OutsBefore baserunners Count BattedBallVelocity PlayResult;
table baserunners*Count*OutsBefore*BattedBallVelocity*BallInPlayType,
PlayResult*N;
run;[/pre]
As for ODS, i was simply outputting a new sas dataset when i executed proc tabulate, as you can see above. Then running proc transpose . . .
[pre] proc transpose data=&dsname(drop = _Type_ _Page_ _Table_) out=&dsname(drop = _Name_);
by baserunners Count OutsBefore BattedBallVelocity;
id PlayResult;
run;[/pre]
Didn't realize proc report had so many options. Oh, and as for the ODS wrapper, i could care less about what it is. Excel i guess because that's what most "laypeople" are familiar with.
I then run the macro for transpose which i mentioned. This has been easy. Not clean, but it's worked.