Avery Label layout

[flybriguy]

hello,

I am creating a layout using an Avery template. With multiple fields to each record is there a way for me to have displayed/printed out onto a single or continous sheets of all those different fields but under the same record with the same info?

Specifically under the avery label template layout I have 3 fields: Name of person, Company, Address . . . . . but with more than one name to each compnay I'm not sure how I can go about doing this. Anybody here get what I'm trying to do here? Seems like it could be a simple solution.

-brian

[Vaughan]

One method is to create related records, one for each company name. Then print the related records.

[flybriguy]

should I then create the relational database with separate "Layout/Report" or a separate database all together? I'm still new at this . . . . . . .

-companies

-names

-addresses

-phone numbers

-email addresses

*all these separate, then make them relational all to one another?

-brian

[Fenton]

One file. Companies is one table, People is another, related by CompanyID (or name, but ID is much much much better). You would print from the People (many) table.

Addresses? Well, do you have multiple addresses per person? If so, are there more than 2? Then another related table. If 2 (and only 2, ever), tough call. I'd probably still use another table, unless it's very clear which address is which and their use.

Do both the Company and their People have addresses, or just the Company? (Often only the company is mailed to, though the People have separate phones and email addresses.)

Phone numbers? Also tough call. You can use repeating fields, with a Type and the number (possibly an Area Code). This works OK, but is not as flexible as a related table, where you can specify a Primary# (not necessarily the 1st entered), to show on list views. I've used both methods. It depends.

Email addresses. Much the same. But usually you only have 1. If you have 2 the 1st is usually primary. A repeating field is OK for this. If you want a "work" email and a "home" email then perhaps separate fields would be best. If you want more than 2 email addresses, with various labels, then another table.

Email addresses come into play when emailing from FileMaker (duh), so if multiple, you have to be able to specify which to use; esp. in bulk email scripts. Also when marking bounced and unsubscribed emails.

You see that the structure of these things, which are normally "attributes," depends on the number of each and their use, in any given business.