I am surprised it does anything for you, since doing it this way launches Blazer without access to its global variables and that, I would expect, should make it crash. Perhaps Blazer notices this and calls SysUIAppSwitch() (which is the right way to invoke Blazer). SysUIAppSwitch(), however, first terminates your application (by enqueing an appStopEvent) and only then switches to the new app.
The only way to launch Blazer while waiting for it to return is to use Accessorizer. It may crash on some devices, and there may not be enough memory on others, but if you want to try it, the Accessorizer API is described here: http://www.1src.com/forums/showthread.php?p=982782 (see post 3). You can bundle Accessorizer for free with your app if you include the license and do not change Accessorizer.prc. A more reliable (but less cool) way to go is just to use SysUIAppSwitch(), and set something up to ensure you return to your app when Blazer is done (e.g., make your app be the default launcher). -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
