For this scenario you should use an approach similar to the find launch
command. First check to see if your app is currently running. If it IS,
then you should have access to the current dmopenRef and also to the
current record. SO, if the record you need to update is the same as
global.currentRecord then you can just use the pointer you've got
currently. Does that make sense?
Alan Pinstein
Synergy Solutions, Inc.
http://www.synsolutions.com
1-800-210-5293
>I'm working on an app that makes use of alarms. The code that executes
>on the alarmtriggered and alarmdisplay launch codes will need to update
>one or more database records.
>
>I'm concerned about the situation where the app is running when an
>alarm occurs. The app will have the database open for read/write, and
>may have done a DmGetRecord on a record that the alarm handler code
>wants to modify. This shouldn't be a problem, since DmGetRecord is
>documented as returning NULL if the record is already busy, and in that
>case I could just feed an event into the event queue that would
>instruct the app to modify the record. However, that is not what
>actually happens; instead a fatal error occurs if I try to get a record
>that's already busy!
>
>Certainly someone else has already addressed this situation. Any ideas
>anyone?
>
>--
>Roger Chaplin
><[EMAIL PROTECTED]>
