Passing trough table

[Radek Michalski]

Hi!

I'm looking for a macro, that let me pass trough all rows in table (ID int -
key, string Name) and everytime calls a query with a Name (or ID) as
parameter. I can't find this kind of macro.
I'm using Access 2000.

Greetings
Radek

[Larry Linson]

You use the Query Builder to create a Query as you describe. Then you can
execute it either from the Query Builder window, from a macro, or from code.

In the Query Builder, select the Table as a data source, pull down all
fields into the Query Builder grid (a short way to do this is to
double-click the table and then drag the mouse pointer down). Then, under
the field you want to use to select the record, for example, the "ID" field,
in the Criteria line, type "[Enter ID to Select]". When you run the Query,
it will prompt the user to enter the ID.

If, by something else you said, you have a field named "Name", that is not a
good idea. "Name" is an Access reserved word and using it for a field name
can be confusing.

Larry Linson
Microsoft Access MVP
"Radek Michalski" <ra*******@op.pl> wrote in message
news:br**********@news.onet.pl...

Hi!

I'm looking for a macro, that let me pass trough all rows in table (ID int - key, string Name) and everytime calls a query with a Name (or ID) as
parameter. I can't find this kind of macro.
I'm using Access 2000.

Greetings
Radek

[Radek Michalski]

Larry Linson wrpte:

You use the Query Builder to create a Query as you describe. Then you
can execute it either from the Query Builder window, from a macro, or
from code.

Hi Larry, thanks for answer.

That's the point, but I want to automate the whole process. I.e. without
prompting for a particular ID system should make some task (run a macro that
runs a query and saves results to another table) giving that macro that ID
as parameter.
So, in other words, I want to pass the whole table by ID field (key) and run
some task for each ID value.

PS: The "Name" field is called in other way in my database.

Greetings
Radek

[Larry Linson]

What you want to do is certainly possible in code, but I doubt you can do
what you want in macros. Where does the code (what you called macro) obtain
the particular ID? It has to come from _somewhere_... unless you just make
one up using the Rnd function.

"Run a query and save results to another table"? That sounds to me as if it
would mean redundant storage of data -- and a violation of relational
database design principles.

Let's begin from the beginning and you tell us what data you have and what
you are trying to accomplish, not just incomplete ideas as to how to do some
unspecified thing. Chances are very high that _someone_ here will have a
useful suggestion.

Larry Linson
Microsoft Access MVP
Larry Linson
Microsoft Access MVP

"Radek Michalski" <ra*******@op.pl> wrote in message
news:br**********@news.onet.pl...

Larry Linson wrpte:

You use the Query Builder to create a Query as you describe. Then you
can execute it either from the Query Builder window, from a macro, or
from code.
Hi Larry, thanks for answer.

That's the point, but I want to automate the whole process. I.e. without
prompting for a particular ID system should make some task (run a macro

that runs a query and saves results to another table) giving that macro that ID
as parameter.
So, in other words, I want to pass the whole table by ID field (key) and run some task for each ID value.

PS: The "Name" field is called in other way in my database.

Greetings
Radek

[Radek Michalski]

Larry Linson napisa³:

Let's begin from the beginning and you tell us what data you have and
what you are trying to accomplish, not just incomplete ideas as to
how to do some unspecified thing. Chances are very high that
_someone_ here will have a useful suggestion.

OK, starting from beginning:

The thing I need to do is to split large table containing lots of data to
small tables and export those into new database (each portion goes to each
new database). The split criterium is the ID I told about existing in
another table.
So the necessary steps are:

1) set focus on the first row of a table containing ID and Name1 field
2) using ID or Name1 field query large table looking for data associated
with particular ID/Name1
3) export query results to another database
4) go to next ID
5) repeat steps 1-4 for all IDs in the index table

The new database needs no relations - it would be a mdb file containing only
the query result.

Greetings
Radek