Quote:
Originally Posted by wibbly
Does it help if you restrict the BB client to running AES (for which there are built-in libraries) and do 2 way sync for the whole database? I would personally find these acceptable restrictions if so, to get editing on the BB.
|
I could do that but think about the scenarios...
Starting with desktop and device synchronized.
On the desktop you modify record A then synchronize.
No problem. You push the file to the device.
On the device you modify record B then synchronize.
No problem. You push the file to the desktop.
On the desktop you modify record A.
On the device you modify record B.
Now you synchronize. Now what?
I'd have to give you the option to...
Desktop wins.
Device wins.
Latest file timestamp wins.
Leave them separate.
Also consider that if you turn on the "mark database as modified on last-access time change" feature, every time you LOOK at an entry, the database changes.
So, I'm still thinking about it. It's not the amount of work involved that's making me hesitant but the "You blew away my database!!!" support issues.