Kevin Wertz

Searched the forums and couldn't find the answer. If I open a new window that goes to a different layout to perform my find, is there an easy way to pass the results of the find to the original window?

Update, I now know why the list isn't popping. It's because the field is defined as a button. When I made a duplicate of the field and cleared the object name of the button field, the value list did pop up on the duplicate field. So I suppose I could nest these fields together. I just hate doing klugey stuff like that tho. Anyone have an idea of how to make the button field pop?

Hi I have a selector field that is not in the tab order and I made it un-enterable as well. I named the field object "SelectorField". The field is a button that basically ends in a go to object script step that sends the user to the SelectorField object. Problem is it doesn't open the value list, it just puts a black border around the field. Anyone know how to make the value list pop open? I don't want to use go to field because I want to use this script on many screens. (when is Filemaker going to give us go to field name by calculation!!!:)

Sounds like what you want is usually referred to as a dwindling value list. "Comment" has posted a DwindlingVL file on here. I used it and thought it was relatively easy to set up.

An update for those who may search and find this thread. I accomplished what I wanted to do with a separate ".New" table occurrence with a tempID on the main TO to the RowID of the related TO. (thanks Soren) I used a tab control with a blank default tab and two other tabs (new row and web new row) that I named as objects. The tabs are small and I hide them behind my "new row" button, which itself is nested in a single-tab tab control (this is necessary to keep you from being able to click the hidden tabs through the new row button). Thanks to whoever posted "tab panel trick" on databasepros.com for this tip. Upon clicking new row the system determines web or client and sends the user to the corresponding tab. Of course the fields from the ".New" TO are there and the user enters the new record (note that no portal is used). Upon clicking the save button on the row the system jumps to the table view layout of the related TO and sets the field used by the main relationship. I also included the main TO's tempID on this screen so the script blanks out the tempID here. The user is unable to click out of the record (in the client) so this record is not committed until the user clicks the save button. I accomplished this by using a LastRecMod control field in the main TO with a validation of "LastRecMod=get(recordmodificationcount)". If the user tries to click out of the record, the custom validation message tells them to click save to save the record. Accordingly if the user tries to click "submit" in IWP it gives them a message about failed validation for the LastRecMod field and they are unable to submit without clicking my scripted save button. (I may close the status area anyway, haven't decided yet). So the bottom line is, all this works great in IWP, the record is not committed until I want it to be, and the scripting is all dynamic. All I have to do to use this on another screen is create the ".New" TO and relationship, copy the template onto a new screen, and rename a few object names and script parameters, and place the new fields. By the way you don't always need a "web new row" tab. The reason you might want to use a web new row tab is when you might have a related display field that shows the description of the related record. This of course doesn't work in IWP without a screen refresh, but IWP displays both fields for value lists that show 2 fields so I just eliminate the description field for the web new row tab and expand the size of the ID field. Thanks to Soren and DJ for their posts.

Søren, the wertz.fp7 file doesn't include a script to add a new record, which is my main issue. I was going to allow editing within the portal. Not sure I like the wertz.fp7 approach for editing as it removes that record from the relationship. If the user escapes the screen, shuts down the app, loses connection, etc., that record is stuck out in limbo somewhere. Edit: oh wait, I think I get it. I could use a tempID relationship to create a new record using the single new record row in the portal of this relationship, and then upon clicking a commit button I could associate it to the main record. However that still leaves the problem that the user can click out of the record without clicking the commit button, thinking they're saving the record, then there's an unrelated record in my child table just sitting out there. I wish Filemaker had given us the ability to choose a script to run upon clicking out of the record for a commit.

Well I'm proud of myself partially. I had thought of that but didn't think to try pop up menu. It didn't work when I tried a drop down list so I didn't even think to try the pop up menu. Thanks for the tip...works great! Edit: bummer, I just checked and it doesn't work over IWP. I can maybe live with this though.--KW

I got most of the way with using globals but I'm stuck on how do I use globals to show related values? In other words if the user select the ID in one field I want a second un-enterable field to show the related name or description from the ID they selected. Soren I haven't looked at the file you sent yet. Going to look now. Gotta leave here pretty soon so I may not post again until Monday. Thanks!

Thanks guys, that fixed it. I had downloaded the dwindling value list sample file from Nightwing but Comment's is much simpler. Thanks!

Oh okay I was referring to Comment's dwindlingvl file that he posted early in this thread. I'm assuming he took a different approach because I did the fix you mentioned and it didn't fix it.

The dwindling value list works great until there are no values in the portal. Tried this in the sample file too and got the same result. Is there a fix for this?

Okay after spending some time on this last night it looks like I'm going the route of global fields for the data entry. The real challenge will be how to make the validations dynamic. I don't mind scripting the validation but I refuse to create a separate script for each portal addition.

Okay you probably popped in here thinking this question was going to be easy...trust me I searched for an hour on here before I posted. Couldn't find an answer. Here's the deal, I don't want to use the empty portal row. I want more control. I had been using a scripted "new row" button that went to the child layout, created a record, came back to the original layout, and went to a designated "New Row" portal but when I do this the record is committed. I'd like to take advantage of the layout feature where it prompts to save the record or makes you click a button to commit the record. If I go to the other layout I have to save the record before I return. I don't want to use globals because I don't want to script field validation (unique, length, etc) And, I don't want to pop-up a window that goes to the child record layout because my solution is painstakingly IWP enabled, and opening a new window in IWP (in case you didn't know) just opens a virtual window which is full screen and you can't resize it and such. I can live with this in some cases, but not for adding portal rows. The closest I got to what I want was using a hidden tab control with two tabs, blank and "new row". The new row button would put the user in the new row tab, go to a single row portal which used the same relationship as the view portal but with the ability to add a record, and went to the last empty portal row. At the end of the row is a save button which commits the record, and reshows the blank tab on the hidden tab control. The problem with this approach is that I can't force the user to click the save button, as they can just click out of the record and the commit will occur. Or in IWP they will click the submit button. Of course when this occurs, my new row tab remains open and there sits the new record that was just added. So did you get all that? I would love a new idea, or if you have an idea of how to fix my "new row" tab control idea I'd love to hear it.

Yeah I used the left function. It just irritated me that I had to. Just wondering if anyone knew why it behaved differently than the client and if there was a way to fix it instead of workaround it.

Sorry I should have been more clear. This is just a boolean checkbox (check the box for "1", uncheck for off). I don't like to use radio boxes in this situation because of the need to hold down shift to deselect. In the client it just puts the "1" in the field, in IWP it adds a carriage return.

Has anyone noticed that clicking a checkbox in IWP adds a carriage return to the end of the value? Any way to make this stop doing this?

That's a great custom function that I will probably use. Thanks! But it's not really related to my issue. I think I will just have to manually create an if statement for each action (script) that I add. I could also create all my actions in one mega script and assign a script parameter to each but not sure I like that idea. Curious to hear if anyone else has any ideas. I still want to hear from someone who has gotten a script trigger plugin to work over IWP. I saw one post on here where someone said eventscript worked with IWP but he has not emailed me back.

I understand all about script parameters and variables. The problem is that Filemaker still makes you hard code the script you want to run. There is no mechanism to select the script you want to run based on the result of a calculation. Without a plug in, in Filemaker I still have to use: If get(scriptparameter)=1 Perform Script "Test" else if get(scriptparameter)=2 Perform Script "Test2" end if and so on and so forth. This gets laborious to maintain for large amounts of scripts. Filemaker ought to allow us to set what script we want to run based on a calculation, or the value of a field, such as: Perform Script (relatedtable1:scriptname) So without this the only way to select a script based on a calc, value of a field, variable, etc., is with a script trigger plug in. Unless someone knows a way to do it without one, if so, I would love to know. In case you're wondering what I'm doing, I have a select action dialog box that filters based on what actions the user has access to. My actions table contains all the "friendly names" along with the actual script names. Every time I add a new script for an action I don't have to make any changes in any other scripts. All I have to do is add a record to the actions table and put in the script name in the script name field. Then the plug-in runs the appropriate script when that action is called. BTW I'm on 9advanced on Windows XP now. I have clicked "My Profile" and don't find where to update my current version info.

Thanks, I don't actually need it for script triggering. I need it for dynamic script selection. In other words when I click a button on a record I want it to run a script named in a related record.

Hi has anyone gotten any of the script triggering plugins (ZippScript, EventScript, FMExample) to work over IWP? I don't even need it so much for script triggering as I need it for dynamic script selection (i.e. if you click a record, it runs a script named in a related record)

Wincontrol works great! Thank you!!!

How do I make a runtime open at a certain size when I send it to someone else? I have FMP8Advanced and of course it gives us tools to size the windows, but what about the whole application? Of course after I resize the app it will open at that size on my computer, but will open maximized when I send it to someone else. Help please!

Can this plug in produce custom dialog boxes? That's what I really need.

Using the two server configuration with Server 7 Advanced, I want to have one machine with Filemaker Server and the web publishing core, then I want to use our company's current IIS server for the web server, hoping they will agree to install the administration console on this machine as well. Just wanted to make sure that Filemaker can share the IIS web server with all the ASP apps our company uses, or does it have to have its own? Also I'm curious if anybody knows if there would be a problem with installing the administration console on our web server. Would it take too much resources, slow down the server, etc.

I have to think that dialog boxes can't be too far behind. What they have done with IWP is very slick IMO, and I have a feeling they will continue to perfect it in future releases.