I have the same problem.  Trying to keep my accesses to the other database
seems like a good idea.  However, I don't believe that there is any guarantee
that
I won't be in the middle of an access when the beam comes in...

Additionally I also have the dual problem.
That is, if the other app (datebook) is running and I get a beam,
I need to access their database.
Other than a complicated scheme such as saving
the data received in a beam and then updating their database when
next I open, does anyone have any ideas??

-robert mckenzie
<[EMAIL PROTECTED]>

-----Original Message-----
From:   Brian Hall [SMTP:[EMAIL PROTECTED]]
Sent:   Wednesday, January 19, 2000 12:10 AM
To:     [EMAIL PROTECTED]
Subject:        Re: Problem with keeping other app dbs open during beaming

>Speaking of questions falling through the cracks, nobody responded to this
>question of mine.  Is that because there is no good solution?  :)
>
>- ---------- Forwarded Message ----------
>Date: Monday, January 10, 2000 4:01 PM -0800
>From: "Douglas I. Anderson" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Q: Accessing PIM databases vs. beaming
>
>Just wondering if anyone else has come upon a solution to this problem.
>
>My situation is that I want to keep the database of some of the PIM apps
>(datebook, todo, memo, etc) open for the life of my program.  The problem
>shows up whenever a beam comes in.  The system calls the builtin PIM app,
>which asks the user whether they want to accept the beam.  Then, the
>system calls again to actually parse the data and store it.  When the PIM
>app wants to store the data, it tries to open its database, which my app
>currently has open (because it hasn't been quit yet).  The PIM app fails
>silently, not telling the user that the data wasn't stored.

One of my own apps has a similar problem - it keeps MemoDB open whenever it
is logging data. I figure (at least in my case) the best way to do it is to
restructure my app to only open the DB when it actually needs to create or
read a record, and then close it back up again. Perhaps you could
re-organize your app in that manner?

Brian

Reply via email to