Troy, Thank you for the below idea, I tried it out and it works perfect for me! It is much more efficient that printing one label at a time with a DECLARE CURSOR routine and allows me to simply process labels from a "stardard" view without having to create temp tables etc. Excellent!
A side note is that I loaded a null record into my primary table (with a unique identifier). I have now easily made a simple routine asking my user how many labels to "skip". In my label design, I simply located variables that checked for the null record. If the column is null they display a space (no print output) and if not the column value. I made the unique identifier on the null record a negative integer so that record will always print first if needed using an order by clause. My program is now setup to print 1 - 99 duplicate labels with the option of skipping 1-10 labels. Just what I was looking for! Thanks again for your suggestion, hopefully I can return the favor sometime! -Bob -----Original Message----- From: Troy Sosamon <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Tuesday, May 14, 2002 9:38 AM Subject: RE: Printing labels - Razzak's Reply >If you want multiple copies of the same record, use a cartesian join. Creat >a view between your primary table and some (temorary or not) table that has >an autonumberd column in it that is not missing any rows. Don't join the >tables on anything, but limit the second table to the # of duplicates you >want. Example: > >names_table: >fname >John >Fred >Bill > >Numbers_table >idNum >1 >2 >3 >4 > >create view name_dup as select t1.fname, t2.idnum from names_table t1, >numbers_table t2 > >I build my report or label to run off of the name_dup view. >Now I print or select from name_dup Where IDNUM <= 3 (or however many rows I >want) > >This is one of those rare situations where a cartesian join is useful. > >Troy Sosamon > > >===== Original Message from [EMAIL PROTECTED] at 5/14/02 6:32 am >>Thanks Lawrence! >> >>You hit on the key which I did not explain very well. >>I wanted to print multiple copies of (1) record on >>the same sheet. I will play around with the temp >>tables some and see what I get. Also, I suppose >>to use a partial printed sheet of labels I could place >>the correct number of rows filled with NULL values >>to "SKIP" over the already printed labels. (Assuming >>I did not have any text box, lines, or graphics on the >>labels.) >> >>Sharon, >> Thank you for your idea about the "multiple" label setup. >>If I decide that I always need (2) labels per record, this >>would be a good way to go! >> >>Thank you all for your input. >> >> >> >> >> >> >>-----Original Message----- >>From: Lawrence Lustig <[EMAIL PROTECTED]> >>To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> >>Date: Tuesday, May 14, 2002 12:40 AM >>Subject: Re: Printing labels - Razzak's Reply >> >> >>>> How do I get the program to print on all (4) labels of >>>> of a sheet? >>> >>>Bob: >>> >>>AFAIK, if you want multiple copies of a single label you need to build a >>>temporary table that has identical rows for each label that you want. >>>R:Base prints one label per row in your source table or view -- there's no >>>way to ask it to "repeat" a given row X number of times. >>> >>>To make sure that your routine is multi-user safe, check out the CREATE >>>TEMPORARY and PROJECT TEMPORARY commands, which will build temporary tables >>>that don't get stored in the database. >>> >>>Alternatively, you could base the label on variables, rather than columns. >>>You still need a table with the same number of rows as labels you want to >>>print but you could just keep a permanent table with enough records around. >>>Then, when you want to print your labels you would set your variables and >>>issue LBLPrint MyLabels WHERE LIMIT = X and you would get X identical >>>labels, based on the variables. >>>-- >>>Larry >>> >>> >>>================================================ >>>TO SEE MESSAGE POSTING GUIDELINES: >>>Send a plain text email to [EMAIL PROTECTED] >>>In the message body, put just two words: INTRO rbase-l >>>================================================ >>>TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] >>>In the message body, put just two words: UNSUBSCRIBE rbase-l >>>================================================ >>>TO SEARCH ARCHIVES: >>>http://www.mail-archive.com/rbase-l%40sonetmail.com/ >>> >> >> >>================================================ >>TO SEE MESSAGE POSTING GUIDELINES: >>Send a plain text email to [EMAIL PROTECTED] >>In the message body, put just two words: INTRO rbase-l >>================================================ >>TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] >>In the message body, put just two words: UNSUBSCRIBE rbase-l >>================================================ >>TO SEARCH ARCHIVES: >>http://www.mail-archive.com/rbase-l%40sonetmail.com/ > >================================================ >TO SEE MESSAGE POSTING GUIDELINES: >Send a plain text email to [EMAIL PROTECTED] >In the message body, put just two words: INTRO rbase-l >================================================ >TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] >In the message body, put just two words: UNSUBSCRIBE rbase-l >================================================ >TO SEARCH ARCHIVES: >http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
