>Except that the browse's valid fires only if the field value has been changed, but a text box Valid(), grid's AfterRowColChange() and such ALWAYS fire on leaving the field.
>

Build whatever functionality you need into the event, or don't - it's your issue. Using subclasses offers greater flexibility IMO.

>>That'd work too.
>>
>>The valid clause on a BROWSE works just like the AfterRowColChange() event when moving off of the current record. The :V clause after a field in the BROWSE command would work just like your solution.
>>
>>-Matt

EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater

---

NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys