How to handle differing behavior in drop-downs in FMP client vs. IWP?

[truthiness]

So many forums, I hope this is right place to post.

My question is how do you handle the difference in behavior between drop-downs in IWP verses the FMP client?

For example, say you have a value list whose values are, say, companyID & you're also showing the values of a 2nd field companyName.

In the FMP client, you'll get a drop-down that shows this info, but after a selection is made only the vendorID appears.

Contrast this to IWP. The drop-down is the same, but after a selection is made, the companyName, not ID, is displayed. (And, yes, I understand the reason for this behavior.)

My question is if you want to have 1 interface for both client & IWP, how do you handle these different behaviors? Any suggestions?

(BTW, using the old trick of placing a "locked" companyName on top of the drop-down companyID works in FMP client, but in IWP, companyName won't update (for obvious reasons) even though a new companyID was selected.)

Hope this makes sense. TIA!

[Vaughan]

"My question is how do you handle the difference in behavior between drop-downs in IWP verses the FMP client?"

Create a separate layout for each (IWP and FMP client) and optimise, optimise, optimise.

[truthiness]

Arg. That's what I thought you'd say but thanks for the reply.

Thing is, that doubles the amount of work & I don't want to play that (losing) game, especially if you get your layouts out of sync ("I made the change here for the client layout, but, d'oh!, forgot to do on the web side!").

It's ashame that FMP doesn't have the option to display the meaningful info (the company name) while storing the significant value (the company id).

Any famous FMP workarounds here?!?