Needing to run automatically 62 append queries

[DSmith]

We have techs sending in tests for CE credits. We now have 62 different
tests and it's become too time consuming to run each query manually plus I
want other staff to be able to do it. When I looked at Macros it only seemed
to let you open one query and not several. Is there a way I can run 62
queries automatically. These queries increase by 4 every year so by the end
of 2010 we will have 66 queries to append to a table. Help would be greatly
appreciated.

 

[KARL DEWEY]

When I looked at Macros it only seemed to let you open one query and not
several.
Just add additional actions --
OpenQuery Query1
OpenQuery Query2
....
OpenQuery Query57
OpenQuery Query58

They will not wait for first to finish before starting the next.

Maybe if you explained a little more of your process, why queries increase
by 4 every year, someone may have an alternate solution.

 

[Steve Schapel]

Hi,

...
They will not wait for first to finish before starting the next.

I agree with Karl, that a series of OpenQuery actions should work for this.
But I think he meant "they will wait for first to finish before starting the
next".

 

[Jeff Boyce]

I agree with Karl, we perhaps don't know enough about your situation to
offer alternatives.

You've described "how" you are doing something, but not why. What business
need are you handling? What is your table structure? How are the "techs
sending in tests"?

More info, please...

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

 

[DSmith]

Sorry for the late response. I'm recovering from surgery which has had it's
ups and downs.
More Info:
We have a newsletter for Continuing Education credits for x-ray. It comes
out 4 times a year with a test in each issue. We scan these tests uisng
ParScore and then import them into Access by the way of append queries into
a table that holds all the scores. The problems is there is no time limit on
these tests. Sometimes we have techs that have to do 90 credits to
reinstate their license. So in any given month we can receive tests from
Issue 1 to 61. I bring in the scores as a table that is always named the
same so that it will link to all the append queries. Then I run 61 append
queries (relating to all the issues published so far) which is stupid. I
just haven't had the time to find out how to automate it. I have to append
3 fields to a table: TECHID, SCORE, DR# (which is the number of the test).

I know I can make a macro for each query but even that seems too much.

Any help would be appreciated.

 

[PieterLinden via AccessMonster.com]

We have techs sending in tests for CE credits. We now have 62 different
tests and it's become too time consuming to run each query manually plus I
want other staff to be able to do it. When I looked at Macros it only seemed
to let you open one query and not several. Is there a way I can run 62
queries automatically. These queries increase by 4 every year so by the end
of 2010 we will have 66 queries to append to a table. Help would be greatly
appreciated.

Maybe your table structure is the problem. Judging by the number of
different queries you need to run and your statement "These queries increase
by 4 every year", it sounds like your structure isn't quite right. If you
have fields in your table that are named after tests, then that's your
problem. Fix that and a lot of your problems will go away. Can you post a
sample of your table structure? No need to post all of it... just enough to
give people an idea of what you're dealing with. (Oh and a few sample
records).

Pieter

 

[Jeff Boyce]

I'm with Pieter ... I'm wondering just how you have your data organized
(i.e., table structure).

Post a description so folks here know what you're working with -- "how"
depends on "what".

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.