Trigger script via return keypress?

[daehl]

Is there any way to automatically trigger a filemaker script action just by pressing return after entering some data in field? I see that there are some plug-ins for FMP to do this, but is there any way to accomplish this in a database published via IWP?

[Søren Dyhr]

Turn to CWP instead, IWP is as modal as it gets, but your problem might be hidden in an unexpected location, usually is it structural issue which have provoked the urge for event trigging.

We need to know context and purpose in this case, and perhaps you for starters should turn our attention to a web interface that really actually does what you're after - my take on it, is that they are rare, the lions share of pages I know of is data submitted and then is next html generated returning indications of where the blunders/typos are located.

In my humble opinion is it penny wise - pound foolish, to set out on an endevour to make IWP'ed pages behave like genuine applications ... the time alone spend on streamlining the HTML issued by IWP are your troubles only justified if your solution should be served for 50+ simultanious users.

I have worked for a company with such ideas goal, I wouldn't say that other tools mightn't do it better, but filemakers niche is elsewhere, groupware - where you instead buy copies of filemaker to each user under some kind of VLA agreement if nessersary.

Both the Binder and IWP sounds facinating as sales arguments, when you decide to purchase filemaker ... but the reality is that they're kind of cul-de-sac only misleading you slightly from getting the gist of the tool, there is actually no excuse for learning a proper development environment and genuine programming, if you wish to earn on the stuff you do inside some kind of licensing of you intellectual rights.

--sd

Edited May 8, 2008 by Guest

[daehl]

Thanks for the response, Søren.

I think I take your point, mostly. I'm not a professional developer though. Just trying to implement a in-house database, that will be used simultaneously by about 50+ users. Yes, IWP seemed very appealing for that purpose rather than purchasing dozens of FMP licenses. And for the most part, the solution is up and running, but I was just curious as to whether there were any IWP compatible plug-ins or tricks that could make the interface a bit more user-friendly.

I hope to have the time to learn more about CWP, but I'm doing this on my spare time at work and don't have much of a web-developer background. I'm trying to pick up some PHP skills next. So this is definitely a learning experience for me. But any advice is appreciated.

Basically, I've created a data viewer interface to a single database containing approximately a dozen related tables. Each user simply needs to enter an ID# (the primary key) to call up a single record in a tabbed layout that displays multiple portals to include the sub-tables. The primary records are already created, so the IWP users don't need to create them, they just need to update existing fields as to information such as production milestones (times/dates and quantities). But some sub-records need to be added: primarily records that assign defined production problem descriptions to the items being produced (for the purpose of tracking lean manufacturing data).

So IWP has allowed me to get a functional interface in place extremely quickly, and the solution has been operational for a few months now, but I'm fielding a lot of suggestions for interface improvement, and reducing keystrokes & mouseclicks are near the top of the list. So I thought I'd see if anyone knew of a trick to make this work.

Thanks again!

[Søren Dyhr]

What I came to think about was, if you reveal a little more about the relational structure, would it perhaps be possible to make another relational structure ... or just solve this issue:

But some sub-records need to be added

With "....allow creation of related record" turned on for your relations. The boxes are java-scripted to hold the entered values until the committing is done. Remember that related records not nessersarily needs portals, if you use what David Kachel calls tired tables will ordinary fields work seamless as if they were not ushered in from a relation away.

http://www.foundationdbs.com/Downloads/WhitePaperForFMPNovices.pdf

--sd