When there is a newer version of the client, the server will send it down. On the WinCE version, this was done with sending a helper app, transferring execution to the helper app, then sending the client to the helper app, and the helper app will then transfer execution back to the updated client app (I know it's convoluted, but that's done to avoid what you mentioned, i.e. a resource can't be updated while being used)
I'm thinking of doing the same with the Palm OS version, only I don't know if the Exchange Manager is the right tool to use in this case, or if there's a simpler way of sending a helper .prc file down to the client .prc =-Tjeng-Bo-> Tom Zerucha wrote in message <[EMAIL PROTECTED]>... >You can't update a resource while you are using it, so the PRC usually >can't update itself (though it could replace resources or any >database). > >What do you need to do exactly? -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
