> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 04, 1999 8:28 PM
> To: [EMAIL PROTECTED]
> Subject: How to automaticaly start an application after reset
> 
> I am trying to have my application run automaticaly after the 
> reset and
> hot-sync.

You will not get the SyncNotify launch code unless you modify a DB.  I think
this DB has to have the same creator ID as your Conduit is set up to
service.  One trick is simply to open a record and twiddle a value each time
you hotsync so that you always get the SyncNotify launch code.  Or, create
an empty database.  In the code that happens after the post-hotsync reset,
if that DB exists, delete it.  That's a sure-fire way to get that SYncNOtify
launch code.

Beware.  One problem I ran into with this was the following - say your
conduit does its thing and you're all poised to intercept the post-Hotsync
reset.  Then some other 3rd-party conduit comes along after yours, does some
other stuff, and causes Hotsync to crash for whatever reason.  Bummer --
will you still receive the SyncNotify launch code that you _should_ get?  I
don't know.  

Also, I think there is a parameter that is passed with an alarm launch code.
You can get it either because an alarm happened, or because the time was
modified (which would mean you need to update the timeout on any 'open'
alarms you have).  You don't want to do Alarm stuff just because the user
did a time change.

This was a while ago, I forgot a lot of this stuff, but I hope this helps
out a little bit.

-Jeff Ishaq
The Windward Group

Reply via email to