Ken speculated:
>Sounds vaguely like it could have been a security feature, but I'm
>certainly willing to consider it a bug. It sounds like beam receive is
>doing the equivalent of a Memory Delete on the application before filing
>the new database.
Why would this be a security feature? There shouldn't be any difference
between installing a new version by HotSync'ing (which doesn't delete
data) or installing a new version by beaming (which evidently does). I
think this is just an oversight (i.e., if not a "bug" then at least a
poor job of defining the product) in the Exchange Manager (or whatever
component it actually is that accepts beamed apps).
Although I must say there probably IS a difference, since after a HotSync
your app is called with a "was HotSync'ed" launch code, whereas after
beaming I don't think the app is called in the same way. Or is it?
Steve Patt
President, Stevens Creek Software
http://www.stevenscreek.com/pilot
The home of...
PalmPrint && UnDupe && AreaCoder && Handy Randy
Athlete's Calculator && PocketTimer && SnailMailer
On Hand && Take An Order! && many more
