Chronus Notes v6 and Treo 680

5 views
Skip to first unread message

Dewi

unread,
Aug 31, 2007, 3:34:28 PM8/31/07
to ChronosTalk
I have just upgraded my Lifedrive for a Treo 680. A few weeks ago
after upgrading Daylite my ChronosNotes Conduit could no longer access
the database. Notes and Daylite seem to work fine.

Firstly has anybody had experience getting the Palm ChronosNotes
Conduit to talk to the database again as I would like to use it to
synchronise my Palm Notes.

Now the best bit. When I first synchronised my Treo via Missing Sync
v6 I tried again to use ChronosNotes Conduit which again did not work.
After a couple of days using my new Treo, I tried to access a few
missed calls and redial using the Call History. Each time my Treo
would reset. I recalled that Missing Sync had a Call History Conduit
so I thought I would open it to see who had called - Now the really
strange bit, no Call History but in each field there was data from
Chronos Notes.

So it would appear, certainly after my first and only sync with
ChronosNotes that the Conduit overwrote the Call History Database.

Very strange.

Does anybody know a good notes application that will synchronise with
my Treo?

Rob & Tammy Murphy

unread,
Aug 31, 2007, 4:10:37 PM8/31/07
to Chron...@googlegroups.com
The problem is Daylite and Notes both use OpenBase. Although they both use
OpenBase, the problem start when DL and Notes use different versions. I
believe the DL currently uses 10.0.8 while Notes uses 10.0.7. This is a
well know issue.

They work around that I use is DL, Missing Sync v6 Notebook feature (to
sync memos or notes from / to Mac). I have replaced Chronos Notes with
DevonThink Pro and have been much happier for making the switch.

Just my thoughts, actual results may very.
___
Regards,
Rob
Sent with SnapperMail from my Palm Treo
www.snappermail.com

...... Original Message .......

db

unread,
Sep 2, 2007, 1:24:40 PM9/2/07
to ChronosTalk
Results may very well vary.

Rob has it right, this has ben an ongoing issue.
I've given up on both apps because of the OpenBase issues. It is a
crazy situation when two apps based on the same database can't work
together on the same computer. It has been an ongoing issue that
shouldn't be, and both developers should have seen it coming, unless
OpenBase kept them in the dark until it was too late.

Reply all
Reply to author
Forward
0 new messages