Report Question

[dave greene]

Hi,

I need some info on what I can do with a report. Can I
update data in a table that is used in a report? Can I
save the data in a report to a table to document the
report?

Thanks in advance.

Dave

 

[Ken Snell]

You can't save the data "from" the report itself, but you can save the data
that are used to create the report. You'll need to give more info about what
you're doing and what your setup is.

 

[John Vinson]

Hi,

I need some info on what I can do with a report. Can I
update data in a table that is used in a report? Can I
save the data in a report to a table to document the
report?

A Report is a tool for moving data from Tables to paper. If you update
the data in the Tables and rerun the report, the new table data will
be printed. You cannot go the other way without a lot of hassle; since
the data in a Report cannot be changed or edited by the user, there's
little point, and in any case there is no way to "save the data in a
report to a table".

Could you describe what the context might be? Why are you trying to do
this?

 

[dave greene]

Please see above response.

Thanks,

David

-----Original Message-----


A Report is a tool for moving data from Tables to paper. If you update
the data in the Tables and rerun the report, the new table data will
be printed. You cannot go the other way without a lot of hassle; since
the data in a Report cannot be changed or edited by the user, there's
little point, and in any case there is no way to "save the data in a
report to a table".

Could you describe what the context might be? Why are you trying to do
this?


.

 

[Ken Snell]

Comments inline....

--
Ken Snell
<MS ACCESS MVP>

This is what I am trying to do.

We have a table of members and a table of projects.
Neither table has any direct relation to the other (but I
have created a third table with it's primary key a combo
of the member id and project id to create a many to many
relationship). Is this the right thing to do?
Yes.


I need a way to choose a member and a project, add some
data and create a printed report (onto a preprinted form).
The customer would like the ability to "add to" some of
the fields with late breaking info. I would like these
edits to be written to the database and track a each
report that is printed.

From your answer, I take it that I will be creating a new
table in order to capture the information, and just using
a report to print the data?

Not necessarily. You can build a form that uses a query as its recordsource.
The query can filter the records as you desire, and, as long as it's
updateable, can allow you to add data to the table (the "late-breaking"
information). This form also could allow the printing of the report by a
command button.

The report can be run using another query that reads the table and, if
necessary, reads controls from the form itself in order to get the necessary
values (though likely all data you'd need would be in the table).