If anyone has found a way to trick it, please post.

It turns out that script triggers are partially supported by IWP (and CWP). From the FileMaker Pro Help: “In Instant Web Publishing and Custom Web Publishing, script triggers can only be activated by a script and not by direct user interaction. For example, if a user tabs into a field that has an OnObjectEnter script trigger, the trigger will not activate. If a script step causes focus to move into that field, the script trigger will activate.”

It turns out that it’s not entirely limited to script-based triggering in IWP. A script trigger will also activate based on a button which performs a script step directly. For instance, a button which performs a commit records command will trigger the layout’s OnRecordCommit event.

It’s far less than what a real web client would give us, but it’s better than nothing!

- Dave

I must confess we don’t use IWP enough to speak very intelligently about it. To your specific questions:

1. Script triggers are not supported in IWP. I suspect of would take a major overhaul of the way interaction works in IWP to get something like this working.

2. There is one report on technnet about poor IWP performance, so there may be some inconsistent bugs to work out, but in general I would expect performance to be about the same.

Server itself has seen some performance improvements, so you may see some speedup, but I don’t think the web publishing engine has been sped up.

Hope it helps,

Geoff

Thanks SO much for your wonderfully detailed review! This just makes me even more excited to get moving with 10.