By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,652 Members | 1,010 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,652 IT Pros & Developers. It's quick & easy.

How to continuously append live table to table?

P: n/a
I have a situation here:

every month there will be a table (with 3200+- entries) that should be
appended to a Year-to-Date table.

I appended the second month's live table to the accumulative table,
but don't know how to do it for the third month, other than deleting
the live table temporarily and import the new live table again.

is there a form or any other simpler and neat way for this? thank you
for your time.

May 31 '07 #1
Share this Question
Share on Google+
11 Replies


P: n/a
On May 31, 3:05 pm, LiDongn...@gmail.com wrote:
I have a situation here:

every month there will be a table (with 3200+- entries) that should be
appended to a Year-to-Date table.

I appended the second month's live table to the accumulative table,
but don't know how to do it for the third month, other than deleting
the live table temporarily and import the new live table again.

is there a form or any other simpler and neat way for this? thank you
for your time.
What objefctive are you attempting to satisfy by having separate month
and year to date tables?

May 31 '07 #2

P: n/a
On May 31, 3:24 pm, DavidB <j...@yahoo.comwrote:
On May 31, 3:05 pm, LiDongn...@gmail.com wrote:
>
What objefctive are you attempting to satisfy by having separate month
and year to date tables?
I need to consolidate the monthly table to YTD table and then make
report based on the YTD Table.

May 31 '07 #3

P: n/a
Li********@gmail.com wrote:
On May 31, 3:24 pm, DavidB <j...@yahoo.comwrote:
On May 31, 3:05 pm, LiDongn...@gmail.com wrote:

What objefctive are you attempting to satisfy by having separate
month and year to date tables?

I need to consolidate the monthly table to YTD table and then make
report based on the YTD Table.
The proper way would be ONE table and then use queries. One for the current
month and one for the year to date data.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
May 31 '07 #4

P: n/a
>
The proper way would be ONE table and then use queries. One for the current
month and one for the year to date data.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Thanks for the reply, and the question is how to create this YTD
data. It has to be updated every month by adding up the current month
tables to the YTD table.

Jun 1 '07 #5

P: n/a
Li********@gmail.com wrote:
>The proper way would be ONE table and then use queries. One for the
current month and one for the year to date data.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Thanks for the reply, and the question is how to create this YTD
data. It has to be updated every month by adding up the current month
tables to the YTD table.
Not if you have it all in one table. You just have a totals query that
looks at all records for the current year by having appropriate criteria
applied.

Any time you have processes that involve copying data from one table into
other tables that is a big warning flag that your design is incorrect.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Jun 1 '07 #6

P: n/a
>
Not if you have it all in one table. You just have a totals query that
looks at all records for the current year by having appropriate criteria
applied.

Any time you have processes that involve copying data from one table into
other tables that is a big warning flag that your design is incorrect.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Thanks a lot, I feel I need to redesign my work. I'm very much a
newbie for Access, any frame idea and design methodology is huge help
to me.


Jun 1 '07 #7

P: n/a
>
Not if you have it all in one table. You just have a totals query that
looks at all records for the current year by having appropriate criteria
applied.

Any time you have processes that involve copying data from one table into
other tables that is a big warning flag that your design is incorrect.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Thanks a lot, I feel I need to redesign my work. I'm very much a
newbie for Access, any frame idea and design methodology is huge help
to me.
Jun 1 '07 #8

P: n/a
Not if you have it all in one table. You just have a totals query that
looks at all records for the current year by having appropriate criteria
applied.

Any time you have processes that involve copying data from one table into
other tables that is a big warning flag that your design is incorrect.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
I'm very much a newbie for Access, any frame idea and design
methodology is of great help to me. Thank you very much.

Another question is following your logic, I will have 12 current
tables for a year and I will make summary queries based upon these
tables. but I still need to go into the queries every month linking
the new current month table into my reports.
Jun 1 '07 #9

P: n/a
Li********@gmail.com wrote:
>Not if you have it all in one table. You just have a totals query
that looks at all records for the current year by having appropriate
criteria applied.

Any time you have processes that involve copying data from one table
into other tables that is a big warning flag that your design is
incorrect.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

I'm very much a newbie for Access, any frame idea and design
methodology is of great help to me. Thank you very much.

Another question is following your logic, I will have 12 current
tables for a year and I will make summary queries based upon these
tables. but I still need to go into the queries every month linking
the new current month table into my reports.
No 12 tables. ONE table. Your report can easily be filtered to show any
particular month of data or year to date.

Just Make a new table and append into it all of your 12 tables worth of data
(include a field for the date if you don't already have one). On a form you
can allow the user to enter the desired report month and then provide a
button for opening the report. That button can open the report pre-filtered
on the desired month or on Year to Date if the user chooses that option.

Once you have all that working you can delete your separate 13 tables that
you have now.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Jun 1 '07 #10

P: n/a
On Jun 1, 10:38 am, "Rick Brandt" <rickbran...@hotmail.comwrote:
LiDongn...@gmail.com wrote:
Not if you have it all in one table. You just have a totals query
that looks at all records for the current year by having appropriate
criteria applied.
Any time you have processes that involve copying data from one table
into other tables that is a big warning flag that your design is
incorrect.
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
I'm very much a newbie for Access, any frame idea and design
methodology is of great help to me. Thank you very much.
Another question is following your logic, I will have 12 current
tables for a year and I will make summary queries based upon these
tables. but I still need to go into the queries every month linking
the new current month table into my reports.

No 12 tables. ONE table. Your report can easily be filtered to show any
particular month of data or year to date.

Just Make a new table and append into it all of your 12 tables worth of data
(include a field for the date if you don't already have one). On a form you
can allow the user to enter the desired report month and then provide a
button for opening the report. That button can open the report pre-filtered
on the desired month or on Year to Date if the user chooses that option.

Once you have all that working you can delete your separate 13 tables that
you have now.

--
Got you. tons of thanks.

Jun 1 '07 #11

P: n/a
On May 31, 5:30 pm, LiDongn...@gmail.com wrote:
On May 31, 3:24 pm, DavidB <j...@yahoo.comwrote:
On May 31, 3:05 pm, LiDongn...@gmail.com wrote:
What objefctive are you attempting to satisfy by having separate month
and year to date tables?

I need to consolidate the monthly table to YTD table and then make
report based on the YTD Table.
That does not answer my question. I asked why you have two separate
tabels to begin with not why you want to merge them.

Jun 1 '07 #12

This discussion thread is closed

Replies have been disabled for this discussion.