Dear everybody.
Is there any way to go to a specific tab in FM v8. For example, if I
have in the tab control setup with three different tabs, is there any
script that permit to go to any of these three tabs? Because if in each
tab I have different portals but I can not go to to a specific portal
of a specific tab using a button.
Thanks,
Jokin

On 5 May 2006 20:31:06 -0700, "Jokin" <joaquin.castilla@gmail.com>
wrote:

>Dear everybody.
>Is there any way to go to a specific tab in FM v8. For example, if I
>have in the tab control setup with three different tabs, is there any
>script that permit to go to any of these three tabs? Because if in each
>tab I have different portals but I can not go to to a specific portal
>of a specific tab using a button.
>Thanks,
>Jokin


Use the Go To Field script step - just set it to go to a field in the
portal on the tab you want.

You can then set a button, or use it as a sub-script or even with
EventScript or zippScript.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
VoicesInMyHead
a.k.a. The Voices
                  No, we're not... Yes, we are...
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Yes, the Go to Field will work

However, you should probably create fields "Tab 01," "Tab 02," "Tab
03," etc. specifically for this purpose, as it will find the first
instance of the field in your layout.  If you move or add that field
somewhere else, it can throw all your hard work off.

Remember to select its behavior so you can't click into it and whenever
you do a Go To Field command, put a Commit Records command after it.

davey

On 5 May 2006 22:00:27 -0700, "davey" <averbach@mac.com> wrote:
>However, you should probably create fields "Tab 01," "Tab 02," "Tab
>03," etc. specifically for this purpose, as it will find the first
>instance of the field in your layout.  If you move or add that field
>somewhere else, it can throw all your hard work off.

If you have a script or button to take the user to the field they need
to be in, and you move it - the script is still valid if the
relationship is listed [yourtable::yourfield].

If you are changing the structure of your database to the extent that
scripts and relationships are breaking, then I agree you should be
using the comments step in scripts or the comments line on the Fields
tab of the Define Database window to better follow your work.  Or
better yet a custom ER diagram that evolves with your database which
lists what the heck you are doing.

>Remember to select its behavior so you can't click into it and whenever
>you do a Go To Field command, put a Commit Records command after it.

I am far from an expert yet, but why would you create a field that the
user can't enter, and forces them to the first/next field, instead of
the field they should be in.  True the first/next field could be the
necessary field, but then again, could not be.  Hmmm.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
VoicesInMyHead
a.k.a. The Voices
                  No, we're not... Yes, we are...
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-