It's hard to answer this without knowing more about your database and layout design.
Which starter solution are you adapting?
Where have you placed these Sales Representative fields?
Generally speaking, you'll need to control which record is being viewed, define more than one Sales Representative field for a given record, or create a table of related sales representative records.
Thanks for your response. I am using the Contact Management Solution. I have one tab that is basic contact information for a customer, then another tab that is titled Purchase History. In that tab, I use fields for: 1) Item 2) Payment Type 3) Total and 4) Sales Representative. Since one customer may purchase more than one item, but not from the same person, I'd like to make the fields usable so they do not copy every time I use one. Thanks again!
If you have one text field placed on multiple layouts or multiple tabs, when you enter data into that field, all the copies of that field in that record will contain the data.
It is also possible that it is a global text field, then when you enter data into the field, all instances of that field in all records will contain the data.
What you are describing is much like an invoice where you have one invoice record that lists multiple items purchased. In a Relational database such as FileMaker Pro, this done by defining a related table of records where one record in this related table is created for each kind of item purchased. These related records are then displayed in a portal. You can see one example of this approach in the Invoices starter solution.
Comment, uploaded a demo file of the same concept that's simpler and easier to understand:
This type of portal can be placed on your tab so that you can list multiple items and have a different sales representative for each item purchased. You'd define your sales representative field in this related table you'll need to define instead of your contacts table.
Great, thank you so much for your help!