printing multiple iterations with a serial number bikeweenie 22.09.2006 01:17:01 I am developing a db that will be used to print questionnaires. I have a form that allows a user to select questions by using a series of combo boxes. I then use a report to place the questions in text boxes and print the questionnaire. This is working, to some degree. What I am having difficulty with is that I want to print a quantity, say 25, of the same questionnaire (report) with a serial number that is printed on the questionnaire and recorded in a history table. I have no idea how to go about this. Can someone help?

Re: printing multiple iterations with a serial number strive4peace <strive4peace2006[ at ]yahoo.com> 24.09.2006 15:20:07 the "cheapest" way to do this is to create a table with, for instance, the numbers 1-50 (or whatever is the maximum number of copies you will allow) *Qtys* Qty, integer records are Qty 1 2 3 etc in a query: use your table and the Qtys table as fieldlists put the items you want printed on the grid and then, this also: field --> Qty table --> Qtys show --> no criteria --> <= QtyToPrint This will cause Access to create the information multiple times in the underlying recordset Warm Regards, Crystal * (: have an awesome day :) * MVP Access Remote Programming and Training strive4peace2006 at yahoo.com * bikeweenie wrote: [Quoted Text] > I am developing a db that will be used to print questionnaires. I have a form > that allows a user to select questions by using a series of combo boxes. I > then use a report to place the questions in text boxes and print the > questionnaire. This is working, to some degree. > > What I am having difficulty with is that I want to print a quantity, say 25, > of the same questionnaire (report) with a serial number that is printed on > the questionnaire and recorded in a history table. I have no idea how to go > about this. Can someone help?

Re: printing multiple iterations with a serial number bikeweenie 25.09.2006 23:51:02 Crystal, I tested your recommendation and I see how the quantity portion works, but I'm still in the dark on how to create a serial number for each copy that is printed. Any ideas? Thanks, dc "strive4peace" wrote: [Quoted Text] > the "cheapest" way to do this is to create a table with, for instance, > the numbers 1-50 (or whatever is the maximum number of copies you will > allow) > > *Qtys* > Qty, integer > > records are > > Qty > 1 > 2 > 3 > etc > > in a query: use your table and the Qtys table as fieldlists > > put the items you want printed on the grid and then, this also: > > field --> Qty > table --> Qtys > show --> no > criteria --> <= QtyToPrint > > > This will cause Access to create the information multiple times in the > underlying recordset > > Warm Regards, > Crystal > * > (: have an awesome day :) > * > MVP Access > Remote Programming and Training > strive4peace2006 at yahoo.com > * > > > > bikeweenie wrote: > > I am developing a db that will be used to print questionnaires. I have a form > > that allows a user to select questions by using a series of combo boxes. I > > then use a report to place the questions in text boxes and print the > > questionnaire. This is working, to some degree. > > > > What I am having difficulty with is that I want to print a quantity, say 25, > > of the same questionnaire (report) with a serial number that is printed on > > the questionnaire and recorded in a history table. I have no idea how to go > > about this. Can someone help? >

Re: printing multiple iterations with a serial number strive4peace <strive4peace2006[ at ]yahoo.com> 26.09.2006 00:12:57 if you want a seperate tracking number for each printed copy, it would be best to make a table and use that -- you will need to match up the answers... won't you? Can you explain more about the purpose of your application? Warm Regards, Crystal * (: have an awesome day :) * MVP Access Remote Programming and Training strive4peace2006 at yahoo.com * bikeweenie wrote: [Quoted Text] > Crystal, > > I tested your recommendation and I see how the quantity portion works, but > I'm still in the dark on how to create a serial number for each copy that is > printed. Any ideas? > > Thanks, > dc > > "strive4peace" wrote: > >> the "cheapest" way to do this is to create a table with, for instance, >> the numbers 1-50 (or whatever is the maximum number of copies you will >> allow) >> >> *Qtys* >> Qty, integer >> >> records are >> >> Qty >> 1 >> 2 >> 3 >> etc >> >> in a query: use your table and the Qtys table as fieldlists >> >> put the items you want printed on the grid and then, this also: >> >> field --> Qty >> table --> Qtys >> show --> no >> criteria --> <= QtyToPrint >> >> >> This will cause Access to create the information multiple times in the >> underlying recordset >> >> Warm Regards, >> Crystal >> * >> (: have an awesome day :) >> * >> MVP Access >> Remote Programming and Training >> strive4peace2006 at yahoo.com >> * >> >> >> >> bikeweenie wrote: >>> I am developing a db that will be used to print questionnaires. I have a form >>> that allows a user to select questions by using a series of combo boxes. I >>> then use a report to place the questions in text boxes and print the >>> questionnaire. This is working, to some degree. >>> >>> What I am having difficulty with is that I want to print a quantity, say 25, >>> of the same questionnaire (report) with a serial number that is printed on >>> the questionnaire and recorded in a history table. I have no idea how to go >>> about this. Can someone help?

Re: printing multiple iterations with a serial number bikeweenie 26.09.2006 02:27:02 My application is one of those beasts with several heads and several masters. The portion I have tried to describe is focused on selecting questions to be printed on a generic [paper] form with designated response areas to be read by an OMR scanner. Through a few preliminary combo boxes where an instructor will identify his program, course, class, test or survey, etc., subsequent combo boxes will be filtered to only reveal appropriate questions from the question table. I am using ADO recordsets to write the form's combo box selections to various tables that will make up a course history. At the same time, I am using the same selections to populate text boxes on a report with a layout that matches the pre-printed boxes on a laser printer form. Right now, my form has a click event that triggers the history writing and opens the report. It all works and I can easily create 1 questionnaire. Up to this point, I have been building a course history, but as you surmised, I need to be able to track the responses individually, not to mention keeping the response data on a multi-page quesionnaire correctly matched. So we arrive at my current issue: how to create an output that generates and prints a serial number for each questionnaire. (In retrospect, my initial question was innaccurate- I don't want the same thing printed say, 25 times, but 25 unique things each printed once.) BTW, I had an awesome day, thanks. "strive4peace" wrote: [Quoted Text] > if you want a seperate tracking number for each printed copy, it would > be best to make a table and use that -- you will need to match up the > answers... won't you? > > Can you explain more about the purpose of your application? > > Warm Regards, > Crystal > * > (: have an awesome day :) > * > MVP Access > Remote Programming and Training > strive4peace2006 at yahoo.com > * > > > > bikeweenie wrote: > > Crystal, > > > > I tested your recommendation and I see how the quantity portion works, but > > I'm still in the dark on how to create a serial number for each copy that is > > printed. Any ideas? > > > > Thanks, > > dc > > > > "strive4peace" wrote: > > > >> the "cheapest" way to do this is to create a table with, for instance, > >> the numbers 1-50 (or whatever is the maximum number of copies you will > >> allow) > >> > >> *Qtys* > >> Qty, integer > >> > >> records are > >> > >> Qty > >> 1 > >> 2 > >> 3 > >> etc > >> > >> in a query: use your table and the Qtys table as fieldlists > >> > >> put the items you want printed on the grid and then, this also: > >> > >> field --> Qty > >> table --> Qtys > >> show --> no > >> criteria --> <= QtyToPrint > >> > >> > >> This will cause Access to create the information multiple times in the > >> underlying recordset > >> > >> Warm Regards, > >> Crystal > >> * > >> (: have an awesome day :) > >> * > >> MVP Access > >> Remote Programming and Training > >> strive4peace2006 at yahoo.com > >> * > >> > >> > >> > >> bikeweenie wrote: > >>> I am developing a db that will be used to print questionnaires. I have a form > >>> that allows a user to select questions by using a series of combo boxes. I > >>> then use a report to place the questions in text boxes and print the > >>> questionnaire. This is working, to some degree. > >>> > >>> What I am having difficulty with is that I want to print a quantity, say 25, > >>> of the same questionnaire (report) with a serial number that is printed on > >>> the questionnaire and recorded in a history table. I have no idea how to go > >>> about this. Can someone help? >

Re: printing multiple iterations ... generating surveys with serial number strive4peace <strive4peace2006[ at ]yahoo.com> 27.09.2006 18:36:22 based on what you said, I see 1. print multiple copies of a survey, each with a unique serial number 2. the survey content varies with user criteria so, each time surveys are created, you should have tables something like this: *SurveyContent* ContentID, autonumber ProgramID, long integer -- program ID from Programs table ClassID, long integer -- class ID from Classes table CourseID, long integer -- course ID from Courses table (may not need to store this since Classes would probably contains it) InstructorID, long integer (again, may not need to store this since class identifies it) SurveyID, long integer -- Survey set that was generated DateCreated, datetime, DefaultValue --> =Now() In the SurveyCriteria table, you store the criteria to create the surveys and match that up with the survey -- I just used this criteria as examples, you can expand on that to include other criteria of course ;) -- if you need this information for historical purposes *Surveys* SurveyID, autonumber survTempID, long integer Qty, integer DateCreated, datetime, DefaultValue --> =Now() *SerialNumbers* SerialID, autonumber SurveyID, long integer SerialNumber, long integer (for the user to reference if you do not want to use the SerialID) DateCreated, datetime, DefaultValue --> =Now() Surveys and SerialNumbers are used to store information when the system prints surveys, and each is uniquely identified *dfn_Questions* QuestionID, autonumber Question, text *dfn_Responses* RespID, autonumber QuestionID, long integer Ordr, integer (order) Response, text *dfn_SurveyTemplates* survTempID, autonumber TemplateDesc, text --> Template Description etc... ID fields to identify it's content *dfn_SurveyQuestions* survQID, autonumber survTempID, long integer QuestionID, long integer Ordr, integer (order) where dfn_ means it is a definition table so that you can print the right questions in the right order Your user interface collects information to create a record in the SurveyCriteria table. The set of questions is identified by the survey template, which is an unbound combo for the user to pick, or determined automatally by definitions in the system and will provide survTempID so the system knows which set of questions to use. Next, the record is created in Surveys, survTempID is filled out, and the quantity of surveys to generate is specified by the user or calculated from class sizes The final step is generating the records in SerialNumbers and then using those numbers for the reports that print all the actual surveys In this way, you have a record of what that unique number goes to for matching answers...and you can also ensure that the same "unique" number does not get used multiple times... I realize that my concept of your structure is most likely different than what you actually have, but hopefully, you can see the logic... Warm Regards, Crystal * (: have an awesome day :) * MVP Access Remote Programming and Training strive4peace2006 at yahoo.com * bikeweenie wrote: [Quoted Text] > My application is one of those beasts with several heads and several masters. > The portion I have tried to describe is focused on selecting questions to be > printed on a generic [paper] form with designated response areas to be read > by an OMR scanner. Through a few preliminary combo boxes where an instructor > will identify his program, course, class, test or survey, etc., subsequent > combo boxes will be filtered to only reveal appropriate questions from the > question table. > > I am using ADO recordsets to write the form's combo box selections to > various tables that will make up a course history. At the same time, I am > using the same selections to populate text boxes on a report with a layout > that matches the pre-printed boxes on a laser printer form. > > Right now, my form has a click event that triggers the history writing and > opens the report. It all works and I can easily create 1 questionnaire. Up to > this point, I have been building a course history, but as you surmised, I > need to be able to track the responses individually, not to mention keeping > the response data on a multi-page quesionnaire correctly matched. > > So we arrive at my current issue: how to create an output that generates and > prints a serial number for each questionnaire. (In retrospect, my initial > question was innaccurate- I don't want the same thing printed say, 25 times, > but 25 unique things each printed once.) > > BTW, I had an awesome day, thanks. > > "strive4peace" wrote: > >> if you want a seperate tracking number for each printed copy, it would >> be best to make a table and use that -- you will need to match up the >> answers... won't you? >> >> Can you explain more about the purpose of your application? >> >> Warm Regards, >> Crystal >> * >> (: have an awesome day :) >> * >> MVP Access >> Remote Programming and Training >> strive4peace2006 at yahoo.com >> * >> >> >> >> bikeweenie wrote: >>> Crystal, >>> >>> I tested your recommendation and I see how the quantity portion works, but >>> I'm still in the dark on how to create a serial number for each copy that is >>> printed. Any ideas? >>> >>> Thanks, >>> dc >>> >>> "strive4peace" wrote: >>> >>>> the "cheapest" way to do this is to create a table with, for instance, >>>> the numbers 1-50 (or whatever is the maximum number of copies you will >>>> allow) >>>> >>>> *Qtys* >>>> Qty, integer >>>> >>>> records are >>>> >>>> Qty >>>> 1 >>>> 2 >>>> 3 >>>> etc >>>> >>>> in a query: use your table and the Qtys table as fieldlists >>>> >>>> put the items you want printed on the grid and then, this also: >>>> >>>> field --> Qty >>>> table --> Qtys >>>> show --> no >>>> criteria --> <= QtyToPrint >>>> >>>> >>>> This will cause Access to create the information multiple times in the >>>> underlying recordset >>>> >>>> Warm Regards, >>>> Crystal >>>> * >>>> (: have an awesome day :) >>>> * >>>> MVP Access >>>> Remote Programming and Training >>>> strive4peace2006 at yahoo.com >>>> * >>>> >>>> >>>> >>>> bikeweenie wrote: >>>>> I am developing a db that will be used to print questionnaires. I have a form >>>>> that allows a user to select questions by using a series of combo boxes. I >>>>> then use a report to place the questions in text boxes and print the >>>>> questionnaire. This is working, to some degree. >>>>> >>>>> What I am having difficulty with is that I want to print a quantity, say 25, >>>>> of the same questionnaire (report) with a serial number that is printed on >>>>> the questionnaire and recorded in a history table. I have no idea how to go >>>>> about this. Can someone help?