Goto Field based on $variable

[Digitalbrit]

Hi there

Is there any way to goto a field where that field is currently in stored in a $variable?

Thanks for any leads ...

Tim

[ralph.nusser]

Give the needed field (e.g. First Name) an [color:blue]object name ( e.g. First Name)-

Now it is possible to go to the field with the

[color:green]Go to Object script step

http://www.filemaker.com/help/Script-Steps21.html

[color:green]Go to Object [Object Name: [color:red]"

Repetition: [color:red]]

The "object name" parameter can be a variable (e.g. $field).

Happy FileMaking Ralph Nusser

Sogetes Computer-Services

http://www.sogetes.com

Edited November 9, 2008 by Guest

[Digitalbrit]

Thanks for this - seems to work a treat. I now just have to name a ton of fields - its a shame that by default object name isn't created. Maybe things are different in 9?

Regards

[comment]

No. There's another method that you could use: loop a Go to Next Field[] until Get(ActiveFieldName) equals your $variable (assuming the field you want is in the layout tab's order).

However, it might be better to ask yourself why you need this, and isn't there a better solution to the real issue.

[Digitalbrit]

Funny you mention this because that is the method I have inherited. I am integrating the

Stored Finds code from Nightwing into my solution and this uses that method.

It works well but doesn't cope with fields over multiple tabs (as in the tab-control), as goto next field appears to cycle around the fields on the current tab. The code is extracting the field from a string into a variable hence I was hoping to goto a field based on that variable.

Alternatively is there a way to goto next field and have this follow the complete tab order. Say fields 1-10 are in tab1 and fields 11+ are on tab2, so when tabbing from field 10 it jumps to field 11 which is on the next tab)?

Regards

Tim

[comment]

Couldn't you simply have your script switch to another layout without tab controls?

[Digitalbrit]

I can do that when reinstating the find (and use GTRR) but the method for "saving" the find is driven from the form with the tabs on it and hence has the same challenge.

I don't fancy rewriting the interface to end up with more forms and scripts if I can avoid it.

I'm experimenting with placing an object at the start of each tab and then having looped around all the fields on a tab, using the goto object to jump to the next tab - this looks to be working.

Its not elegant but is a decent compromise as it works for the save and find, means you don't have to name every object and allows me to keep using tabs without the need for more forms and script. Fingers crossed I have a result.