startup find

[nopposan]

Hello all. I'd like to have a layout default to display a particular set of found records.

Generally, how is this accomplished without requiring the user to click on a button?

Thank you.

[bcooney]

If you wish to use FM's built-in layout popup menu in the left-hand status bar, then there is no way to also perform a find and switch layouts without a script.

Can you be more specific? What layout, how do you envision users getting to the layout, what found set do you wish to have as the default?

[nopposan]

If you wish to use FM's built-in layout popup menu in the left-hand status bar, then there is no way to also perform a find and switch layouts without a script.

I did envision that users would use the popup menu in the status area to navigate to the layout. However, I can't recall learning any other way for them to get there other than by a script in another layout; if they get there that way then I know I can just build the find into the same script. Hmm . . . I suppose I could build a separate layout as a kind of home page with buttons that bring up other layouts. 'Not sure that's the best solution though.

I don't think the specifics of the layout are really relevant; but, it's a data entry form with many fields, most of which are in portals -- It does contain buttons that bring up other layouts that may display data from other tables.

Thank you for your willingness to help.

Oh, you asked about the found set; I want the layout to display only proband samples and not parents or other relatives whose samples are usually only used for confirmation testing.

Edited May 29, 2008 by Guest
'Forgot to respond to a question.

[bcooney]

Systems that require stuff to be done when switching between layouts usually have scripted navigation. You can take the Main Menu route, or have nav buttons at the top of each layout, or both.

Beware of building finds into navigation, however, especially if you are finding on an unstored calc field. These finds can be slow (esp as the record count grows), and users will be frustrated when they navigate to a layout that has a such a built-in find.

[nopposan]

Beware of building finds into navigation, however, especially if you are finding on an unstored calc field. These finds can be slow (esp as the record count grows), and users will be frustrated when they navigate to a layout that has a such a built-in find.

Oh, thank you for the tip.

Well, this part of the project is being put on hold anyway though; I've just learned that another DB project and our Laboratory Information Management system are going to take on this functionality. Well, let's see if their plans succeed . . . until I hear otherwise, this one sits on the shelf.