A resaonable approach to managing data?

Folks,
>
I at the proverbial fork in the road and before I make a decision, I
was hoping maybe I could get some advice. I'm in the process of moving
data to Access. I'd like to use Excel for charting.
>
Consider this typical scenario for a second, and decide let me know how
you would handle it.
>
>
1) 210,000 record table exists in Access
2) Data request came in as follows: number of deer checked at each
check station, by county, by district - very simple
3) Created a query to grab just the fields I needed. Saved the query.
4) Started Excel and pulled the data via MS QUERY.
5) Brought the data into Excel as a Pivot Table.
6) Manipulated a couple of things and sent the workbook as an email
attachment.
7) Saved the workbook.
>
To me, seems like a lot of steps and duplication of data. I've stored
data in Access and Exel both. If someone wants that Pivot Table
resent, I've got to try and remember where I put it. I'm trying to
cut down on duplication and clutter. Seems like I should have done
this all from Access. Yes/no?
>
I would love to hear from others on how they would have handled this.
I might mention, I probably will need a similar table next year, with
next year's data. Other than that, I'll probably never use that
particular Pivot Table again.
>
Thank you so much for all of your help.
>
Mike

I know most people are really upset Access
doesn't have a pivot function to change
columns to rows, but if you do a little
research on arrays you can create your
own pivot function. It's not as fast as,
say, SAS's "Proc Transpose", but it
does work.

"ManningFan" <manningfan@gmail.comwrote
>>
I don't know _where_ you manage to get all your (mis-)information. Access
has, since the 16-bit days, had CrossTab Queries which change columns to
rows; and for the last two versions, Access 2002 and 2003, has had both
Pivot Table and Pivot Chart functionality, in addition.
>
Larry Linson
Microsoft Access MVP

I'm still using A2K, so I didn't know
about the new functionality. As
of A2K if you wanted to do a true
transposition of data you had to do
it with an array.
>
Peyton Manning
Microsoft Access MVP

I know most people are really upset Access doesn't have a pivot
function to change columns to rows

ManningFan wrote:>
How do you know that?

ManningFan wrote:>
How do you know that?

Because I talk to alot of users.
>
Peyton Manning
Microsoft Access MVP

Because I talk to alot of users.
>
Peyton Manning
Microsoft Access MVP
>
Lyle Fairfield wrote:

"A lot of users" (that you talk to) = "most people"? The notion of
changing columns to rows is entirely at odds with what a database is;
it's like being upset because cabbages don't come with their own
condoms.

I guess the folks at SAS need to be made aware that their "Proc
Transpose" (which has been in use for over 10 years) is useless, and
the folks at Microsoft need to be told that adding pivot functionality
to Access is a stupid idea. Hell, while we're at it let's remove the
Pivot command from SQL Server 2005 since it goes against the grain.
>
Because Lyle has all the answers, right?

>ManningFan wrote:
>>
>Useless is in the eye of the beholder; it's useless to me.
>Yes.
>Yes.
>Sometimes, Yes; sometimes, No.

"ManningFan" <manningfan@gmail.comwrote
>>
Well, "Peyton," (or, maybe that should be "Don" or "Steve"?)

It's not Steve (PCD). The English is far too good and there aren't nearly
enough of these: "!!!!!!".
>
Keith.