Send a record from a Form to a Table.

  • Thread starter SteelFire via AccessMonster.com
  • Start date
S

SteelFire via AccessMonster.com

I have a form that looks at one record at a time, and I need to be able to
click a button that will make a list of records. (click it for each record
you want on the list) Then be able to out put that list as a printable report.
I have a table to store the list, I just don't know of any commands to send
the single record that is active to a table. the rest I am sure that I can
figure out.
 
K

Klatuu

There are a couple of different ways to consider. One would be launch an
append query from the form with a command button that would add the current
recurd to a table that would be the data source for the report. Another
would be to add a boolean field to your table and use that in a query as the
report's data source.
 
J

Jeff Boyce

Are you saying that you "build" a table in order to create a report (from
that table)?

If so, it may be possible for you to skip that step altogether! Many
reports in Access can be based on an underlying query, rather than a table.

If you can define the set of records you want to report on via a query, use
that query as the source for your report.

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
S

SteelFire via AccessMonster.com

how would I go about the append query?
There are a couple of different ways to consider. One would be launch an
append query from the form with a command button that would add the current
recurd to a table that would be the data source for the report. Another
would be to add a boolean field to your table and use that in a query as the
report's data source.
 
K

Klatuu

There are too many ways to be able to give you detailed instructions.
I would probably not even use that method. It was really to show you an
option.

I would suggest you add a yes/no field to your table and update that as
needed to include in your report. Use a query as the reports record source
that filters for only those records with a Yes (True) in the new field.

The other thing then, is to determine when you want to reset the True
records to False for the next report run. That would be a simple update
query to change all records to false.
 
S

SteelFire via AccessMonster.com

Ok, so I have a database full of different mechanical parts. I already have
reports set up for things like the Customer it was used for and the Type of
job it was. That way we can look back and see what we used. Now, I am needing
to make a list of my choosing from any part in the database. They may not
have anything to do with each other, so I can't have a preset way to filter
like the others do. Lets say we are making some new thing, so I will go and
find all of the parts that could apply to this new thing. I could print them
out so that my boss could over look them and we would go from there. But it
could also be only one or two parts that we need. I also would need the list
to stay for more then just that time I make it, so that I can go back and
look at it, and make what changes I would need to without re-finding
everything. Does that help?

Jeff said:
Are you saying that you "build" a table in order to create a report (from
that table)?

If so, it may be possible for you to skip that step altogether! Many
reports in Access can be based on an underlying query, rather than a table.

If you can define the set of records you want to report on via a query, use
that query as the source for your report.

Regards

Jeff Boyce
Microsoft Office/Access MVP
I have a form that looks at one record at a time, and I need to be able to
click a button that will make a list of records. (click it for each record
[quoted text clipped - 4 lines]
the single record that is active to a table. the rest I am sure that I can
figure out.
 
J

Jeff Boyce

I may not have a clear enough picture yet, but it still seems to me that you
could use a single report that lists the parts you're describing, regardless
of the "new thing".

Then, you'd just need to build a query to 'gather' the parts in one place,
and base the report on that query.

Or, you could use the append query approach and a "report-from-me" table, as
suggested elsethread...

Regards

Jeff Boyce
Microsoft Office/Access MVP


SteelFire via AccessMonster.com said:
Ok, so I have a database full of different mechanical parts. I already
have
reports set up for things like the Customer it was used for and the Type
of
job it was. That way we can look back and see what we used. Now, I am
needing
to make a list of my choosing from any part in the database. They may not
have anything to do with each other, so I can't have a preset way to
filter
like the others do. Lets say we are making some new thing, so I will go
and
find all of the parts that could apply to this new thing. I could print
them
out so that my boss could over look them and we would go from there. But
it
could also be only one or two parts that we need. I also would need the
list
to stay for more then just that time I make it, so that I can go back and
look at it, and make what changes I would need to without re-finding
everything. Does that help?

Jeff said:
Are you saying that you "build" a table in order to create a report (from
that table)?

If so, it may be possible for you to skip that step altogether! Many
reports in Access can be based on an underlying query, rather than a
table.

If you can define the set of records you want to report on via a query,
use
that query as the source for your report.

Regards

Jeff Boyce
Microsoft Office/Access MVP
I have a form that looks at one record at a time, and I need to be able
to
click a button that will make a list of records. (click it for each
record
[quoted text clipped - 4 lines]
the single record that is active to a table. the rest I am sure that I
can
figure out.
 
S

SteelFire via AccessMonster.com

Ok, thanks for the help. I now have a working report-table-query thing going
on. A cmd. runs a query that appends records into a table and the record
reads off of that table. So, all things are working just as I hoped they
would.

Jeff said:
I may not have a clear enough picture yet, but it still seems to me that you
could use a single report that lists the parts you're describing, regardless
of the "new thing".

Then, you'd just need to build a query to 'gather' the parts in one place,
and base the report on that query.

Or, you could use the append query approach and a "report-from-me" table, as
suggested elsethread...

Regards

Jeff Boyce
Microsoft Office/Access MVP
Ok, so I have a database full of different mechanical parts. I already
have
[quoted text clipped - 41 lines]
 
Top