Same field vertical & horisontal (Table View)

[Daniel N]

I'm trying to get a field to fill up the Layout like this:

Scene1 (record 1) - Scene1 (record 2) - Scene1 (record 3) - Scene1 (record 4) - Scene1 (record 5)

Scene1 (record 6) - Scene1 (record 7) - Scene1 (record 8) - Scene1 (record 9) - Scene1 (record 10)

Scene1 (etc.......) - Scene1 (etc.......) - Scene1 (etc.......) - Scene1 (etc.......) - Scene1 (etc.......)

Scene1 (etc.......) - Scene1 (etc.......) - Scene1 (etc.......) - Scene1 (etc.......) - Scene1 (etc.......)

But whatever Layout Type I choose I can only get it to show the records like this:

Scene1 (record 1)

Scene1 (record 2)

Scene1 (record 3)

Scene1 (record 4)

Scene1 (record 5)

Scene1 (record 6)

Scene1 (record 7)

Scene1 (record 8)

Scene1 (record 9)

Scene1 (etc.......)

Scene1 (etc.......)

[LaRetta]

Hi Daniel,

Well, you can create a new layout and specify Labels but the only way to view the result is in Preview Mode. You may be able to use a cartesian join to this table and place one-row portals across the layout (specifying first portal row 1 and only 1 row; specifying second portal row 2 and only 1 row and so on). But it will be limited and a bit of a kludge.

This is a very uncommon need in this business and it may suggest that your design is not optimum in some regard. I susupect that you should be using two tables (Scenes and whatever else makes up these individual records). Can you explain more why you want this?

LaRetta :wink2:

Edited April 15, 2009 by Guest
Corrected typo

[Daniel N]

Hello LaRetta and thanks for your response.

I'm working for a movie company and we want a overview of all scenes for the movies we make. So the plan was to have a table like I described earlier, basically a graphical representation of the progress of the movie. When a scene is finished, it's green... when it's a work in progress its yellow... when it's not even started it's red.

I've got the color part already figured out, so I only need to get the table working.

It doesn't have to be in the order I wrote earlier, just as long as I get the scenes spread over both Vertical and Horisontal.

you can create a new layout and specify Labels but the only way to view the result is in Preview Mode

Yes, but we want to be able to click on the scenes to go to them.

Edited April 15, 2009 by Guest

[LaRetta]

Well, you can't fire a script on a row in Table View. Either way, you will need to use a form layout. But again I wonder what is represented by each record - are they Acts? You can just place regular buttons across a layout and attach a script parameter to each with the button number which would jump to the record. Or you can use portals, or even repetitions.

But it would help if you provided a sample file showing what you have (structurally) so we can see what you will need. Because I still feel that Scenes should be one table and the records you refer to should probably be another table.

Yes, but we want to be able to click on the scenes to go to them.

It doesn't sound like you want to click on the Scene ... it sounds like you want to click on a RECORD of a specific scene. Please provide more detail about what the records represent.

[Daniel N]

Hello again,

I tried your "cartesian join"-portal suggestion and it was exactly what I wanted. So the last thing to figure out is how to make each portal record a link to its record.

Please provide more detail about what the records represent.

This is the setup:

Table 1 - Scenes:

Here we have a layout where the user creates a record and enters in all info about a scene. In our current project we have 40 scenes... so that's 40 records. Each record has it's own name, for example:

SNOW, PHOTO, DIARY, JUMP

Table 2 - Status Overview:

Here is the layout we're talking about. At the moment it looks like this ([] = a portal)

[sNOW] [PHOTO] [DIARY] [JUMP]

[Etc.] [etc.] [etc.] [etc.]

Table 1 and Table 2 are has a "cartesian join"-relationship as you suggested. And each portal is assigned as:

Snow is Initial Row 1, Photo is Initial Row 2, Diary Initial Row 3, Jump Initial Row 4, Etc. Initial Row 5... etc etc.

So all I need now is that, when you for example click on [sNOW] on "Table2 - Status Overview", FileMaker will go to record SNOW on "Table 1 - Scenes".

*edit*

If there only was a way to look up the content of the portal row you click on, like Get(ActiveFieldContents). If that was possible on Portal row, then I could just have a script that made a search for the ActivePortalFieldContents.

Edited April 16, 2009 by Guest

[LaRetta]

In our current project we have 40 scenes... so that's 40 records. Each record has it's own name, for example:

SNOW, PHOTO, DIARY, JUMP

We are still missIng each other. Your original example shows Scene1 record 1, Scene1 record 2 etc. So each of these 'records' within a scene are SNOW, PHOTO and so forth? What are these 'pieces' called?

What if you enter the records out of order and SNOW is not the first Scene1 record added? Using the portal method will not work if you expect SNOW to always be the first position record.

You don't need that second table at all! And what happens when you move to Scene2 - will you continue in the same Scenes table? Your overview table should be your Scenes table and instead of cartesian join, it should be self-join which combines the Scene Number and the Piece name you are clicking on for the jump. Then if you wish for consistency on where each scene 'piece' is placed on a layout, use simple buttons with script parameter attached with the piece name (oh, check attached demo).

But I am also concerned on how you will stop Users from entering two Scene1, Photos? Anyway, I do not feel at all comfortable with my understanding of what you need but hopefully the attached will help a bit. If you can always assure the order of the pieces (records per scene) then maybe portal is the way to go but it sounds like more work than simple buttons. And if you don't care about the order of the pieces on the layout then we can deal with that as well.

Scenes.zip

[LaRetta]

I just reread this:

It doesn't have to be in the order I wrote earlier, just as long as I get the scenes spread over both Vertical and Horisontal.

Okay, but how many 'pieces' will there be? If not in the order you first requested then can they be alpha order? You can use portal if you wish but the theory will be the same, ie, clicking the portal row will set the gPiece with the selfjoin piece name instead of script parameter. Be sure to disallow entry into the portal field (piece) in browse mode) when you attach your script to it.

Edited April 16, 2009 by Guest

[LaRetta]

Here's the method using portal. Notice that I have Scenes and 'pieces' in different tables. In this way, the display of available pieces is right on the Scene page.

I realize that the issue is this: I have no context nor purpose from which to base my answers. I was thinking this was like film Scenes, Acts etc. Is it like a photo gallery? Regardless, I'm still confused on multiple scenes and what the multiple 'pieces' represent.

Scenes2.zip

Edited April 16, 2009 by Guest

[Daniel N]

We are still missIng each other. Your original example hows Scene1 record 1, Scene1 record 2 etc. So each of these 'records' within a scene are SNOW, PHOTO and so forth? What are these 'pieces' called?

Oh I'm so sorry for the confusion. It should be Scene1, Scene2, Scene3 etc in my first example, I forgot to change the numbers when I copy-pasted.

I can add a couple of screenshots after I'm finished with the design and hopefully that will clear things up a little

[comment]

I may be missing something, but perhaps it could be much simpler than it seems?

Scenes.fp7.zip

[Daniel N]

I may be missing something, but perhaps it could be much simpler than it seems?

That's exactly what I meant!

I understand how you made the "go to"-scene buttons, but how did you make so for example "In Progress" shows as blue and "Completed" shows as green in the Scenes-table? I'm looking at your script but I can't find anything that controls the colors.

My current way of adding colors based of status is very clumsy, it's basically just a colored text-field in the background... and a button which executes a script that puts a colored ASCII in a field for each record.

( Btw here are my screenshots anyway:

http://img155.imageshack.us/img155/6025/browse.jpg

http://img201.imageshack.us/img201/7513/layouthaf.jpg )

Edited April 16, 2009 by Guest

[comment]

See:

http://www.filemaker.com/help/html/edit_layout.10.13.html#1028330

[Daniel N]

Thanks! And thanks LaRetta!