AnsweredAssumed Answered

WebDirect -- eliminate returns within fields

Question asked by disabled_ScottKoontz on Dec 3, 2013
Latest reply on Feb 13, 2017 by user19752

Unfortunately, "go to next object using" didn't make it to WebDirect. For example, clients will continue to enter 11 <ret> 12 and not know that they have entered two values.


If I used keystroke trapping, then I fear there would be a lot of processing overhead. If I used post processing, I'd have to make assumptions about what the client wanted; did they mean 11 or 12?


What would be the most efficient way to trap for returns in many fields? I'm not excited about using a script trigger for every text and number field on every layout, but it's quite possible this is the only way.