I have put into my application a function to beam itself to another Palm.
This is using the sample code on the Palm web site, using the ExgPut() and
ExgDBWrite() functions.
This works fine for most databases, however in one instance I have to beam
the app DB itself (works fine), then the app's plugins, which are resource
DB's, with a type of 'HmPl', and various creator ID's (ie. different to the
main app's creatore ID). I do this with successive iterations of the
ExgPut()/ExgDBWrite() calls, but with an Alert popped up in between to wait
till the other user has tapped 'Accept'.
When the other user taps 'Accept' when a plugin has been received, their
unit gets a Fatal Exception.
Has anyone noticed this? And is there any way around it?
I don't know what is so different about these plugins. They're just
resource DB's, although they are open (using dmModeReadOnly) at the time of
the beaming, which shouldn't be any problem. Is there some launch code that
they are sent on the other Palm? ie. does it assume the resource DB is an
app or something crazy like that?
thanks in advance.
SP.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
