getting portal to exclude records

[sflynn]

I have set up a table for all my media assets and I track the type by having the user select a dropdown list to select what type of media they are entering for each record (tape, cd, still image) etc.. I have a related table that is my project table and when the user views the project table I have a portal showing all the assets that associate with that project (no problem). What I want to do is have the user go to a layout where they can see the media assets listed in their separate catagories in scroll-able lists.... if I could get the portal to run a calculation that would do the trick, or is there some other method? Thanks for any help you can give.

[ThatOneGuy]

Hi sflynn:

The techniques you're asking about are actually kind of fun, and I'm happy to help. You have some choices, but it may be best to give it some thought. Below are a few questions:

• How many different Types of media assets do you have? You mentioned "tape, cd, still image, etc." Sounds like there's more. Do you think the list of Media Types will grow in the future?

• Will your database be "served up" in a Multi-User environment, or are you designing for a Single User scenario?

• Screen real estate ... Do we have much space to work with on the layouts? Have you had a chance yet to work (or just play) with the Tab Control panels feature of FM8.5? If you decide to have individual portals for each Media Type and if real estate is somewhat limited, do you think the Tab Panel approach will suit your needs?

• How are you getting along with relationships (in FM)? Do you have a pretty good understanding of how they work and how to create them, or is that an area we can also work on?

• Finally, would you be able to post a "zipped" copy of your file?

From those questions, you've probably figured out it comes down mostly to whether you want/need truly individualized portals, or a single portal with a "filter" the User can change on-the-fly.

What do you think?

[sflynn]

Wow, lots of questions, here's what I know.... there won't be too many different types of media given they are top teir groupings... meaning I have other sub groups under them. I would like to to have this be multi user capable, I think the tabs would be a good way to utilize real estate. In terms of relationships, I think I have a decent grasp although you don't know what you don't know. I would be grateful to have some help looking at my structure as I am pretty new to this but I wouldn't want to post it for the general public. Any help you can provide would be very much appreciated.

[ThatOneGuy]

Hey, sflynn! Sorry it took me a little time to get back to you.

... although you don't know what you don't know.

Isn't that the truth ... for all of us!

Well, I thought it best to just include a sample file for you to inspect and dig around in.

The crux of it is it's use of "constants" on the parent side of relationships. For each type of media, you need a constant to match up through the relationship. That's why it's important to know if your categories are relatively finite.

These constant fields are globals, so if you're modifying an existing system that's currently "served up," you'll need to take the files down, create and populate the globals, then fire it up again on the server ... so that the values in the global fields "stick."

There are two tables in the file: Projects and Media. I created just two layouts and only the barest of minimums needed to illustrate the concepts.

Take a look at the Table Occurrence Graph and how each of the relationships are defined.

Let me know whether it makes sense and whether it's what you had in mind. :goodluck:

MediaTypes_categoryPortals_01.fp7.zip

[sflynn]

Wow, thank you so much for putting that together! I figured it was something like that.. My question then is what are you doing with the "X" not equal to in the relationship between the two tables. I've never used that. Also, if you have a second, I've got another post regarding many to many relationships that I'm stuck on. Again, thank you for the time spent doing that demo!

Steve.

[Ender]

The X symbol indicates a cartesian join, meaning it matches ALL records in the table, regardless of the values of the keys.

[sflynn]

I figured it matched all records, but what do you gain from that? I know this is basic but I had to ask.