need conceptual table design direction

  • Thread starter Thread starter mark kubicki
  • Start date Start date
M

mark kubicki

I have a table with an undetermined number of records...
typically, I have "a" report that prints all of the records in the table

I need to set up an undetermined number of additional versions of the report
(query...) where only prespecified records of the table are included, the
only criteria for a record to be included would be by the user's random
choice -there would be no data determined criteria (ex: not everyone who
lives in "New Jersey" just the folks I designate as living there, or who I
think live there, or who I think ought to live there)

ex:
report001-version_A - include records: 1, 2, 3, 4, 5
report001-version_B - include records: 1, 3, 5
report001-version_C ....

if this were a spread sheet, I would have all of the records listed in rows,
and then each time I added a version of the report, I would add a new column
for it, if a record were to be included in that report, I would enter a "Y"
the intersecting field, else an "N" (this also allow me to compare which
records were being included in different versions of the reports while also
giving me a comprehensive look at what was being included in the report I
was currently choosing for...

in Access, i'm lost

(great at Excel, O.K. enough at VBA, not so O.K. at ACCESS)
thanks in advance,
mark
 
One way to do what it sounds like you want is to add a flag column - MyPrint.
Then in the query for the report set criteria to print all that you have
flagged.
Then run an Update query to remove the flags before starting next time.
 
almost
except that one version of the report DOES NOT supersede the previous,
multiple versions may exist at the same time, so each record needs to know
which report it is included in and which it is not... I could add a flag
column for each version of the report, except the number of reports is
unknown.
 
almost
except that one version of the report DOES NOT supersede the previous,
multiple versions may exist at the same time, so each record needs to know
which report it is included in and which it is not... I could add a flag
column for each version of the report, except the number of reports is
unknown.

Use one RECORD per value - not one FIELD per value.

You need a third table with two fields - ReportNo and RecordNo. If
Report AAB contains records 1, 3, and 5, this table would have three
records:

AAB 1
AAB 3
AAB 5

Base the Report on a query joining this table to the table containing
the records.

John W. Vinson[MVP]
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top