I have a layout with a dropdown showing postcode areas. The postcode areas are linked to a portal. When I change the dropdown it shows the correct related records in the portal, BUT if I try this on my IWP'd page it does not refresh the portal contents.

Any ideas?

IWP is more modal in it's behaviour than native, so for each entry must a commit be issued to refreshen or send a new web page to your browser.

This is a straight forward limitation with IWP you need to think of a workaround to solve. If you instead make the selection via an extra portal is there just enough provision to hide a commit step in the transfer of the ID to the record in question.

The thing is that IWP takes at least 3 times more time to develop apps for than native mode, and I can't help thinking that IWP as gestalt is chosen in penny wise pound foolish manner, probably initiated by a salesman with a greased tongue.

Do the math yourself ... how many hours of extra work could you afford instead of buying genuine clients for your solution. When it comes to it is IWP not scaling sufficiently to be a webstore, here are a mySQL php solution much more likely to fit.

--sd

A little "trick" I employ is to make the whole background a button to do the commit (or other such actions). In native FMP you get the same effect of committing when you click outside a field.