It's stuff like this that makes me wish they had put in a WHEN clause for READ EVENTS like they used to have for the old READ where it would be a piece of cake dropping out of an application if TIME() > tValue.


>It also won't fire if the VFP menu or a popup is active, or if VFP is running a tight loop with no UI interaction within a single procedure or method. It also will not interrupt a single long running SQL statement. The timer will fire (repeatedly) in these circumstances, and timer messages will queue up until VFP changes procedures or runs a UI statement that allows it to check the message queues.
>
>Bela Bodecs has a file in the Files section that is less vulnerable to having the event not detected where you anticipate these types of programming conditions.