The Cartesian join is a great approach, but there is one thing to be careful of:
Be sure users don't have the opportunity to browse such a view. If you have 1000 copies of every row in the address table, and you have 5000 addresses, this works great where your application limits retrieval to a single address and a finite number of copies of that address. But if a user opens the view for browsing without a WHERE cluase like the one Dennis illustrated, the view has 5,000,000 rows in it, and that could tie up some resources! Bill On Thu, 21 Nov 2002 05:14:32 -0500, J.M. GRATIAS wrote: >Create a view which does a Cartesian join of your address table with >the Numbers table. >CREATE VIEW ManyLabels AS SELECT colame1, colname2, .... + >FROM Addresses, Numbers >Notice there is no join clause. This view returns 1000 copies of every >row in your address table. >Create a label definition on that view. >Then you can say >LBLPRINT MultiLabels WHERE AddressID = .vAddressID AND NumberID between 1 and 30 >Congratulations for this very simple and very clever idea !!! >This list is definitively GREAT .... ================================================ 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/
