I have a database with of names of people and a database with seat locations at tables. I can make the table assignments; however, I would like to be able to graphically represent the table.

How can I have one Layout that shows multiple records not in a list view. IE if I have 20 stools at the table, I would like the 20 records around a table. Each could drop down with the names. I can get all of the relationships to work, except I can't get the Layout to graphically look like a table. I can only use the standard list view.

Any ideas?

Edited November 25, 200916 yr by Guest

This is pretty much the same as this - structurally speaking:

http://fmforums.com/forum/showtopic.php?tid/176396/post/204083/#204083

...bear in mind that portals can be cut up and each ... be allocated to fit a graphic presentation.

Take a look at this ...

http://fmforums.com/forum/showpost.php?post/323871/

--sd

Søren, you rock...I hadn't even noticed the initial row option in portals...even though I have used number of rows!

Thanks!

I have it up and running. Is it always sorted by creation order? So once it is layed out..you can't delete from the middle and any added ones go to the end?

It looks like there is no way to sort it. It always is in the order of creation. Is that correct? Any way around it?

Thanks!

Any way around it?

Yes you haven't studied the first link I gave you!

--sd

K. I will study again. After I got the plane working, I didn't look at the calendar again.

Edited December 1, 200916 yr by Guest

Okay. So, I think I get it. Neither example was sorted. They both used the records in the order that they were created. If you choose to, you can sort them. If you don't sort them, or unsort them, then they are returned in the order that they were created.

Did I do okay?

Huh?

What you need is an extra table holding records enough - exactly the number of seats required, then do you need a globla field in that table for selecting the appropriate show ... the bookings is written with both parameters show and seat....

--sd

I am actually thinking that I would generate all seats for each day like the calendar rather than just one set of seats like the plane. I do lots of reports of unused seats, change prices of seats, and audit how the seats were used. I think a separate record would give me the most flexibility.

Do you agree?

All is working great. Thanks for the help.

Do you agree?

Excellent point you bring up there - the opposite (calculated) would be a convoluted - when the more straight forward is asking for it!

--sd