OK ... but what does "it's database" mean? ALL
databases that share the same creator code? I'm
not so sure this would be desirable.
If the app itself does not support a beam operation
for it's database(s), then you could get something
like ZarfCatalog, which allows you to select any
database on the device and beam it.
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi./sec ... not just a good idea, it's the LAW!
> -----Original Message-----
> From: Schettino, John [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 13, 2000 1:13 AM
> To: '[EMAIL PROTECTED]'
> Cc: '[EMAIL PROTECTED]'
> Subject: RE: Beaming a palm app and its database...
>
>
> When the Palm OS beams an app, it just beams the app
> resources database
> records, right? Could you not write a "beam app and database"
> option that
> would beam the app and its database as two actions? The
> receiving Palm would
> see two beam txns, but the sending user would only need to perform one
> transaction.
>
> - John Schettino
>
> -----Original Message-----
> From: Jeff Small [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 12, 2000 2:23 PM
> To: [EMAIL PROTECTED]
> Subject: Beaming a palm app and its database...
>
>
> We need to be able to beam both the app and the database.
> Currently, only
> the app is possible.
>
> The idea has been expressed that it should be possible to somehow
> associate a database and an application in such a way that the
> "beam application" operation would beam the database too. Though
> I haven't been able to find any documentation about such a
> feature, experimentation indicates that it doesn't exist: a
> non-built-in app on my Palm VII is called KVM, and it uses a
> database called "KVMClassDB". Both the app and the database have a
> creator of kJav. Both the "Delete" and the "Beam" menu items on
> the application launcher's menu show a single entry, for the app,
> but a size that includes that of the database. Deleting the app
> also deletes the database. But beaming the app does *not* beam
> the database, and there is no separate facility that I can find
> that can beam the database.
>
> We could always write our own facility for beaming the database,
> and add it to the application. That's actually fairly easy. The
> user would be faced with a rather ungainly two-step process to
> beam first the app, then the database, to another Palm. Should
> we do this? Are there any other ways of doing this?
>
> Anyone's help would be most appreciated.
>
> Thank you in advance.
>
> Jeff Small
>
>
>
>
>
