一种可靠的数据管理方法？ [英] A resaonable approach to managing data?
问题描述
伙计，
我在路上的众所周知的岔路口，在我做出决定之前，我希望我能得到一些建议。我正在将
数据移动到Access。我想使用Excel进行制图。
考虑一下这个典型场景，并决定让我知道你将如何处理它。
1）Access中存在210,000记录表
2）数据请求如下：每个检查的鹿数量
检查站，按县，按区 - 非常简单
3）创建一个查询以获取我需要的字段。保存了查询。
4）启动Excel并通过MS QUERY提取数据。
5）将数据作为数据透视表导入Excel。
6）操作了一些东西并将工作簿作为电子邮件发送了
附件。
7）保存了工作簿。
对我来说，似乎有很多步骤和重复数据。我已经在Access和Exel中存储了
数据。如果有人想要转发表，那么我必须尝试记住我把它放在哪里。我正在努力将b $ b减少重复和混乱。好像我本应该从Access完成
这一切。是/否？
我很想听听其他人如何处理这个问题。
我可能会提到，我可能需要一张类似的桌子明年，有明年的数据是b $ b。除此之外，我可能永远不会再使用那个
特定的数据透视表。
非常感谢您的帮助。
Mike
Excel对于数据操作来说肯定更容易，但是有一些平均值
编码技巧你可以在Access中重现Excel部分，
从而减少重复数据。
我知道大多数人真的很不高兴访问没有一个枢轴
函数来将列更改为行，但如果你对
数组进行一些研究，你可以创建自己的数据透视功能。它没有那么快，
说，SAS的'Proc Transpose'，但确实有效。
Takeadoe写道：
< blockquote class =post_quotes>
伙计，
我在道路上的众所周知的岔路口，在我做出决定之前，我
是希望也许我可以得到一些建议。我正在将
数据移动到Access。我想使用Excel进行制图。
考虑一下这个典型场景，并决定让我知道你将如何处理它。
1）Access中存在210,000记录表
2）数据请求如下：每个检查鹿数
检查站，按县，按区 - 非常简单
3）创建一个查询以获取我需要的字段。保存了查询。
4）启动Excel并通过MS QUERY提取数据。
5）将数据作为数据透视表导入Excel。
6）操作了一些东西并将工作簿作为电子邮件发送了
附件。
7）保存了工作簿。
对我来说，似乎有很多步骤和重复数据。我已经在Access和Exel中存储了
数据。如果有人想要转发表，那么我必须尝试记住我把它放在哪里。我正在努力将b $ b减少重复和混乱。好像我本应该从Access完成
这一切。是/否？
我很想听听其他人如何处理这个问题。
我可能会提到，我可能需要一张类似的桌子明年，有明年的数据是b $ b。除此之外，我可能永远不会再使用那个
特定的数据透视表。
非常感谢您的帮助。
Mike
" ManningFan" < ma ******** @ gmail.comwrote
我知道大多数人真的很不高兴访问
不会''有一个枢轴功能可以改变
列到行，但是如果你做一点点b / b
研究数组就可以创建你的b / b
自己的数据块功能。它没有那么快，
，SAS'的'Proc Transpose'，但它确实有效。
确实有效。
我不知道_where_你设法获得所有（错误）信息。访问
自16位以来就有了CrossTab查询，它将列更改为
行;对于最后两个版本，Access 2002和2003，另外还有
数据透视表和数据透视表功能。
Larry Linson
Microsoft Access MVP
CrossTab查询并不是真的可以做到这一点，他们当然不会
像枢轴表一样工作，或者不需要包括他们在
Access 2002/03。
我还在使用A2K，所以我不知道新的功能。如果您想要对数据进行真正的换位，那么你需要做一个真正的数据转换
它带有一个数组。
Peyton Manning
Microsoft Access MVP
Larry Linson写道：
" ManningFan" < ma ******** @ gmail.comwrote
我知道大多数人真的很不高兴访问
不会''有一个枢轴功能可以改变
列到行，但是如果你做一点点b / b
研究数组就可以创建你的b / b
自己的数据块功能。它没有那么快，
，SAS'的'Proc Transpose'，但它确实有效。
确实有效。
我不知道_where_你设法获得所有（错误）信息。访问
自16位以来就有了CrossTab查询，它将列更改为
行;对于最后两个版本，Access 2002和2003，另外还有
数据透视表和数据透视表功能。
Larry Linson
Microsoft Access MVP
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
Excel is definitely easier for data manipulation, but with some average
coding skills you could probably reproduce the Excel part in Access,
thus reducing duplication of data.
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.
Takeadoe wrote: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
"ManningFan" <ma********@gmail.comwrote
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.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
CrossTab queries don''t really do the trick, and they certainly don''t
work like pivot tables or there''d be no need to "include" them in
Access 2002/03.
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
Larry Linson wrote:"ManningFan" <ma********@gmail.comwrote
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.
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
这篇关于一种可靠的数据管理方法？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
