I am familiar with launch codes, segments, and the fact that globals are not always available. I don't believe that to be the problem in this case, as even with PilotMain reduced to an absolute minimum it still occurs. This appears to a problem specific to the placement of the Exchange Manager dispatch table. Apparently, there are known problems with Exchange Libraries in Applications (ELIAs) in Palm OS 5.x. I'd like to have solution working for Palm OS 3.5 and up, so may have to consider moving the Exchange Library out to an external database. -- Andr�
-----Original Message----- From: LionScribe [mailto:[EMAIL PROTECTED] Sent: Thursday, September 18, 2003 8:36 PM To: Palm Developer Forum Subject: RE: Exchange library within multi-segment application? Most probably this function is being called even when the application is not running, therefore global variables are not always available. Therefore only the first segment is available. So the solution is, to move all those functions to the first segment. LionScribe -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Andre Schoorl Sent: Thursday, September 18, 2003 8:38 PM To: Palm Developer Forum Subject: Exchange library within multi-segment application? I am trying to get this working. I can compile and run Palm's ExgDemoB without problems but when I encorporate the code into my multi-segment app, it crashes in the dispatch table when I call ExgNotifyReceive(). Are there any tricks with segments, startup libraries, or code locking that I should be aware of? -- Andr� -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
