![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
FM 8 Adv., Macs. Is there any way to select an existing window in which to display related records with the GTRR script step? I have a navigation layout that pops up, the user selects a record from a dynamic table, and that triggers the GTRR step. But then my only options seem to be to display the result in the window holding the navigation table or to open a NEW window, neither of which is desirable. I'd like to return the user to the original window that spawned the navigation window, but now focused on the related record. Any help gratefully welcomed... |
#3
| |||
| |||
|
|
FM 8 Adv., Macs. Is there any way to select an existing window in which to display related records with the GTRR script step? I have a navigation layout that pops up, the user selects a record from a dynamic table, and that triggers the GTRR step. But then my only options seem to be to display the result in the window holding the navigation table or to open a NEW window, neither of which is desirable. I'd like to return the user to the original window that spawned the navigation window, but now focused on the related record. Any help gratefully welcomed... |
#4
| |||
| |||
|
#5
| |||
| |||
|
|
First, apologies for the imprecise description of my dilemma... I'll try to be more helpful: I am starting from a layout that shows records from a large table of names/addresses etc. The user can click a "Find" button that produces a pop-up window that contains a global "name" field which is related to the originating table (using an exploded-text calculation of the last name: i.e., they type the first couple of letters of the name into the global field, <tab>, and names starting with those letters appear in a list in the same pop-up window). Once the name they're looking for appears, they click on it and GTRR takes them to that related record in the table of names/addresses. I don't want the original layout to morph into the nav layout then back into the original layout... that's too busy. I just want the user to see the pop-up, click on the name, and go BACK to the original layout focused on the correct record. If I could use "Select Window" as part of the GTRR script step, it would solve my problem, but I don't think I can. If there's an easier way of doing all this, I'd be interested... thanks again. |
#6
| |||
| |||
|
|
The key is your sentence 'they click on it and GTRR takes them to..'. In any case, that action of 'clicking on it' launches something. If that 'something' is only the line 'Go to Related Record', you can't help it asit will go to that record and that's it. But if you change that 'something' into 'Perform Script', in that script you have full control. ie you may put first the line go to GTTR, then add 'Go to your previous layout' followed may be with a 'halt'. Does this work this time ? Remi-Noel "lansingoogle" <filemaker (AT) jillo (DOT) com> a écrit dans le message de news: 1167839300.605365.50610 (AT) a3g2000...oglegroups.com... First, apologies for the imprecise description of my dilemma... I'll try to be more helpful: I am starting from a layout that shows records from a large table of names/addresses etc. The user can click a "Find" button that produces a pop-up window that contains a global "name" field which is related to the originating table (using an exploded-text calculation of the last name: i.e., they type the first couple of letters of the name into the global field, <tab>, and names starting with those letters appear in a list in the same pop-up window). Once the name they're looking for appears, they click on it and GTRR takes them to that related record in the table of names/addresses. I don't want the original layout to morph into the nav layout then back into the original layout... that's too busy. I just want the user to see the pop-up, click on the name, and go BACK to the original layout focused on the correct record. If I could use "Select Window" as part of the GTRR script step, it would solve my problem, but I don't think I can. If there's an easier way of doing all this, I'd be interested... thanks again. |
#7
| |||
| |||
|
#8
| |||
| |||
|
|
I expressed my comprehension a little too quickly. Still confused. Because the GTRR script step requires either Current Layout or a New Layout to display the result of the step. It doesn't allow you to specify an already existing window. So I can't have the selected record displayed in my original window, unless I do a somewhat involved Find process (which still wouldn't give me my desired result: the original SET of records, in the original window, with the focus shifted to the user's selected record). My goal was to have the user start from the main window, pop up the navigation window, and then return to the main window with focus on the selected record. I guess I could do this with a bunch of "Freeze window" steps in the script, and simulate the return to the original window by viewing the related record in a window that's identical to the original and closing the original, but that's an awkward way of doing something that seems as if it should be simple. I guess I'm still searching for an answer. thanks, Lanse Stover |
#9
| |||
| |||
|
|
I expressed my comprehension a little too quickly. Still confused. Because the GTRR script step requires either Current Layout or a New Layout to display the result of the step. It doesn't allow you to specify an already existing window. So I can't have the selected record displayed in my original window, unless I do a somewhat involved Find process (which still wouldn't give me my desired result: the original SET of records, in the original window, with the focus shifted to the user's selected record). My goal was to have the user start from the main window, pop up the navigation window, and then return to the main window with focus on the selected record. I guess I could do this with a bunch of "Freeze window" steps in the script, and simulate the return to the original window by viewing the related record in a window that's identical to the original and closing the original, but that's an awkward way of doing something that seems as if it should be simple. I guess I'm still searching for an answer. thanks, Lanse Stover |
![]() |
| Thread Tools | |
| Display Modes | |
| |