By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,830 Members | 682 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,830 IT Pros & Developers. It's quick & easy.

Creating custom labels design question

P: n/a
Hello,

I have a situation where I have to create 20 labels for each instance of an ID-each of the 20 labels
has a different test number on it but needs the same id and one of 3 project names--for each label I
need:

ID number
Project name (there are currently 3 but will be more in the future)
Test number: There are 20 different tests for each ID number
Also--the ID number has to either be created in sequence from the last used id number, or the
numbers can pre-exist and they need to be flagged that they were printed

I was thinking of this:

A table for each project with ID numbers and project name, and a flagged field that records whether
a label was printed

A table with the 20 different test types

A form that allows the user to choose the project and how many Id's they want to print labels for at
each sitting.

Queries for each project that are not joined that produce a test type for each ID (20 records per ID
:['id, test1; id test2, etc,] This query would search the unflagged records only.

A label report that acts off of this query and prints a label for each ID/test type

I need to do this in Access as instructed, rather than a label program.

1. Is this design feasible? Or is there a differnt way to lay this out?
2. Also--it seems simpler to have each id/project table already populated with the numbers that will
be used than to auto-create them. The id's will be sequential in each table anyway--I would need
about 300 in each table.
3. If this design is feasible--how do I constuct the query to grab the user specified number of
id's from the table?
thanks for any advice
Bob

Nov 12 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.