Performance Issues :Tabbed folders vs Layers

[Jarvis]

I have a database that has a half dozen linked tables.

As I develop this, I am going to need about 100 different layout views.

I can do this with lots of separate layers or I can do this with fewer layers and more tabbed folders within those layers.

My question is about efficiency and speed.

As the user navigates through this database would there be any performance issues favoring one approach over the other?

[bcooney]

Yes, form views with filtered portals may have performance issues, but I've never had them. I'll leave the performance part of your question to others. I suppose it matters what record count, hardware and network speeds you throw at this.

However, I'd like to correct the terminology that you use in your question. Restated:

"I have a database (FM File) that has a half dozen related tables. I am going to need about 100 different layouts. I can do this with lots of separate layouts or I can do this with less layouts and tab panels with portals to the related tables."

There aren't layers (in the sense that you describe) in FM nor are there tabbed folders (they are called tabbed panels).

In my experience, you'll need a form and list view for each major entity in your solution. I also built a dedicated Find layout for each table. I've rarely built a form view without a tabbed panel of portals.

[mr_vodka]

I would much rather have less layouts with a few tab panels than over 100 layouts. There is no significant performance issues. However, if you have a portal with thousands of records, a bunch of summary fields, or ESS fields, you will notice the load time. But in those cases, it would really matter whether its on a new layout or tab now would it.

[Jarvis]

Thanks guys and guy-ettes?

Just the info I needed to plunge ahead!

[bcooney]

Guy-ette?