Hallo,

I am new here and would like to greet all ya first - nice place !

After posting and answering to another thread here I wanted to leave a question here and would like to ask for help on this:

I am on a db table containing an extra global field which will contain text from a choice via pop up / value list which is modified thru' the "show all values of field "x" in the table" step.

So if I (the user) would choose a list item in the layout, the global field will be filled with the content of this field "x" from a certain record of this db and can be used as a keyfield to this record. or not?

Shouldn't I be abled to navigate this way via this pop-up, maybe by using a self-joined relationship from the gobal field to the keyfield of the value list and a GTR button in the layout?? I made a try - but it didn't work ... - Can anybody give me some advice if it works(how?) or why not ?

Thanks, Mo

Globals cannot be indexed and cannot be used as keyfields. However, I think I understand what you want to do: select an item in the value list and go to that field/layout. You could use EventScript with a Go to Field script step in the auto-enter calculation for that field to do it. EventScript is a free plug which enables a script to run upon leaving a field.

I see! - I think you mean the 24H Event Script. Am I right?

Thank you very much for your help.

PS: Do you think there is a chance for globals in future. Wouldn't be great?

BTW: Does it need to be a global for that GTR ??

thanks - thanks - thanks

Little Momo

EventScript is from Softwares for Humans. The field doesn't have to be a global for that Go To.

Since you're on Mac could it also be done with applescript - investigate upload:

--sd

navigate.fp7.zip

As you can now set the clock to pause for half a second or less, it might now be more accurate to run exit scripts involving a "Pause/Exit" script.

Change pop-up to menu on Windows for it to work...

BTW, would someone check if the GoToField ( ) is now cross platform or if we should still look for the platform and then go to the next tabbed field on layout if Win ?

PauseAndRun.zip

Transpower said...Globals cannot be indexed and cannot be used as keyfields.

What? A global can indeed be used as a key field and a GTRR works to go to the related record - in a self-join or another table or even another file. You can jump from the table with the global to the table with the real ID. You can join a global text to any text field and jump to the related record using GTRR. You simply can't GTRR back the other direction, as globals relate to all records.

Mo, if it didn't work for you, I suspect your GTRR pointed to the wrong relationship. Two examples:

Example A)

1) Global text in main table called gCustomerID (popup).

2) Create another table occurence of your main table called SelfJoin.

3) Join Main:gCustomerID to SelfJoin::CustomerID.

4) You are on a Main layout

5) Your script would be: Go To Related Record [ *Show Only Related Records from Table SelfJoin ] and you can even stay on the same layout.

Example

1 - 3 would be the same but ...

4) You are on a SelfJoin layout.

5) Your script of: Go To Related Record [ Show Only Related Records from Table Main ] ... would give you all records because globals are the same for all records in MAIN. You can tell it won't work by looking at your relationship graph. The line from your Main table global to SelfJoin is straight line where it connects into the SelfJoin box; however the line from SelfJoin back to Main is sideways T. The sideways T indicates it can't relate back that direction, ie, can't pass data through it.

* Show Only Related simply indicates you want to end up with a found set of only that specific ID. If you don't click this, you will still go to the SelfJoin CustomerID, but your found set will contain all records.

So in this example, if your Value List is based upon Main:CustomerID, you can attach it to your global and can use script to jump to (or isolate) any specific record within Main that you wish.

Transpower said...select an item in the value list and go to that field/layout.

Mo wants to go to another record, Transpower, not a field or layout. Record-jumping via GTRR works very well.

Thanks for all your support... thanks for all the advices, I have really appreciate it.

But - if it is ok I would like to mention that I already knew the solution using a timed script (like Ugo has mentoined 2 reply-levels back) and I have decided once, that this is not the way I would like to solve the problem. there are several tutorials about that and some example files around in the internet, which has shown me how it works. And to be honest - the application was too shaking from my point of view while running the moment of the script. It feels more like something is going wrong for a second and if I ever would decide to give this solution to clients I would like to have it more in a stabil look. SO I will try the S4H Event Script in Combination with a self joined relationship and will let you know how it works...

PS: @

Gaston's plug in (S4H) is just cool and efficient.

thanks Ugo, Let me give it all a try and I will come back making a report for whom it may concern

Greetings, Lil' Mo ...

Hi there Ugo

"BTW, would someone check if the GoToField ( ) is now cross platform or if we should still look for the platform and then go to the next tabbed field on layout if Win ?"

It is my understanding that the issue is more which popup is used. Scripted popup lists simply don't behave on Windows (they don't want to always pop) and I've heard that on Macs, scripted popup menus pop too much - or it may be the other way around! One of the first things I did with vs. 7 was script a popup list and all I remember is in wonked out - kept popping or kept closing.

This I can say - there is no behavior change between scripting popup menus from vs. 6 to vs. 7. I am clueless about Macs however. If designing xplat, I believe one would still need to provide both popups (stacked). And therefore the platform test, Go To Field[ ] and then Go To Next Field[ ] (on Windows), tab order and stacking order will still be required to pull it off effectively.

Your attached popup list pops for me but not consistently. It only pops 60% of the time. Even adding a Commit Record/Request didn't help it out.

LaRetta