Record appears in...

I figured I would ask this before I start yankin out my hair.

I have vendors and technicians that are assigned to jobs.

Is there a way where in the vendors/techs detailed record that I can show what jobs they appeared in?

I can do this from a text box but it might get a little messy.  Portals perhaps?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

a portal is effectively the solution to display records fields from another table which is related to the main table

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
CruizectrlAuthor Commented:
Happy Monday!  Hope Easter went well for you!!

Theres ways to find and sort within the portal correct?  I dont know why its taking me so long to understand portals.
>Theres ways to find and sort within the portal correct?

Sorting: The order of records in a portal is determined by the definition of the relationship the portal is based on. You can also choose to apply a separate sort order to the portal if you like, but this may slow down your layout if there are a lot of records in the portal. To show the records sorted in a different order, you change to a layout with a different portal that has the sort order you prefer.

You can do a find for values in a portal, but this will return the set of main table records that have SOME related record which matches. This is usually not what you want.

If you want a way to "filter" or restrict what shows up in a portal, you can add a global field to the relationship, which allows you to narrow down what records appear in the portal by typing in some criteria. This can be useful for producing a specific interface effect, but is pretty specialized, and requires adding new fields and relationships.

Generally, it's easier and more flexible to just use buttons and scripts to switch to a separate layout that shows the information sorted how you want.

>I dont know why its taking me so long to understand portals.

A portal is basically a "window" to a set of related records. When you define a relationship between two tables, each record in the main table may be related to one or more records in the related table. The portal is just a way of showing the records from the related table on the same layout with a record from the main table.

You can have multiple portals on a layout, based on different relationships, but you can't have a portal-within-a-portal. Portals are always a list view.

If you've used Access, portals are sort of like Access subforms, though more limited.

You can put a button in a portal, and when you click it it will act on whatever row is highlighted. This is real handy for deleting a row, for example.
The comments above by lesouef and billmercer are really good but am I right you may need more basic guidance?

Let's say, you have got three tables in your file: vendors, techies, jobs. Define whatever fields you need in those tables. Define at least some unique ID field in each of them, which can be done by auto-filling the field with an incremental number. Also, make sure that the jobs table has got a "vendor ID" field and a "techie ID" field.

Now create the relationships between the tables. Create for instance the relationship that links the ID field in the techies table with the "techie ID" field in the jobs table. Do a similar thing for the relationship between the jobs table and the vendor table.

You're half way.

The layouts you're gonna make now each have a different purpose. First, make a layout that is going to be used to enter a new job. You could put the field "techie ID" of the jobs table on that layout and you could format it as a drop down menu that displays all values in a valuelist which is defined as the contents of the ID field and the "name" field in the techie table.

Do the same on that same layout for the vendor. Use this layout to create new job records, and simply pick a value (techies and vendors) from the respective drop down menus (provided you've set up the techies table and vendors table first otherwise your drop down menus will be empty).

Now, the layouts with the portal. A portal is a window through which you look at the related records of a related table. Create a new layout, based on the techie table. Create a new portal on that layout, assign the relationship with the jobs table to it. The relationship is based on the techie ID field in both tables: if they match, then all job records will show up in the portal.
Fill the portal row with the relevant field from the related table (make sure the relationship of the fields is the same as the relationship of the portal or it won't work).

You can create a similar layout for the vendors table.
Your next step could be to jazz up your layouts a little, adding buttons to perform tasks such as "create new job" and tabs to navigate from one layout to the other.

Let us know how it is going.
good luck

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
FileMaker Pro

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.