The LiveField control is a field in your database, except that each key stroke updates the field, and triggers any other calculations (validation, relationships, etc) based on that field, without running a script or committing the record.
Live filtering can creates an as-you-type search effect using a portal. Each character entered narrows down the records that match, enabling you to type only as many characters as are needed to find a unique match. No scripts are involved and the record is not committed.
As-you-type can validation allow you to do things like light-up (or enable) a button as soon as valid data has been entered - you see this a lot with license codes, but its also useful for email addresses, phone numbers passwords, and more, when you want to ensure the data has been entered correctly.
What's more, because the field is a Reactor control it can easily be hidden or disabled too - no more conditional formatting tricks, hidden tab tricks or dodgy portals surrounding the field to make it hide and show!
|1||fieldName||Field to filter on. Must be enclosed in quotes and be the full Table Occurrence::FieldName form.|
|Text or name of a field containing “enabled” (the default), “disabled”, or “hidden”, or a calc which returns one of those 3 values.|
|Default is white, but you can specify the color: see “Background Color” in the “Basics” section.|
|The name of a script to run once loaded.|
|A parameter for the script above.|
LiveField ( "Home::Filter Entry" ; "enabled" ; "rgb( 0, 0, 0 )" ; "Focus LiveField" )
A numeric field, NumDays, is to be validated as the user types, to be no more than 30. A calc field contains the validation test: If( Numdays ≤ 30 ; "OK" ; "TOO BIG!" ). A WebViewer is set up for the entry of NumDays: LiveField( "Home::Numdays" ). The following screenshots show the result of the user having typed 21 and 213.