Long delays after upgrade from 3.2.6 to 3.4.1 on old platform
Because I'm using Life Balance on an old platform - a Visor Deluxe with Palm OS 3.1H3 - I was avoiding upgrading Life Balance, since I thought that you weren't making it a high priority to fix problems on this platform. However, the lure of upcoming new features finally made me upgrade, especially since your website said you were still supporting "Palm OS 3.0 or later" (http://www.llamagraphics.com/LB/palm/index.php).
While Life Balance 3.4.1 is still usable, it can take up to 4 minutes to delete an item; update the To Do list; cancel an update; or select the Time tab when the "Happens" field is "By Date Book" and the due date isn't caught up (e.g., the due date is every day, and I haven't done the task for more than a day or so). As you might suspect, my outline is rather long, with 470 items on it (including recently checked off items). Life Balance 3.2.6 was quite usable, with much shorter delays; e.g., if I started an update when entering a store, it was finished by the time I got to the first aisle I wanted to do shopping in.
It seems that I would have been better off not upgrading Life Balance. I saved my databases before upgrading, but I've made a lot of changes since then. What would be the easiest way to revert to 3.2.6, if that turns out to be the best option for me? I don't have the Windows or Mac version to display my outline on, if I were to make changes to the database by hand.
Is Life Balance going to be inherently and noticeably slower from now on on old platforms like mine? If so, can any of the new changes to Life Balance be made optional, while still making new features available?
Would my databases have been changed when I upgraded?
Barry
Comments
Things to try...
First I would do a "verify data" to confirm that the Outline is sound. It may take a while, so be patient with that process. It isn't fast, but it is quite thorough.
See how that goes.
Other things to try include purging the calendar/datebook. Purging Life Balance of older data.
After that, I would suggest that you open a ticket in the support center, and we can investigate in more detail.
Best wishes,
--Catherine--*
Thanks!
Hi Catherine,
The problem is solved. The "verify data" found that the data was "inconsistent" and repaired it. Updating the To Do list now takes just 33 seconds - quite acceptable for a big outline on a slow processor. The other slow functions are back to taking no more than a second or two.
Thanks!
Barry
Terrific!
Thank you too Barry for getting back to me to let me know that "verify data" worked out for you!
I'm glad I was able to help get you back on track again.
--Catherine--*
The problem came and went again
Unfortunately, the problem came back, at least with updates. Then it went away, after I just did another "verify data" (which didn't find any problems). It seems like more time is needed before calling this matter closed. I'll try to post again after I've used Life Balance some more.
Here's our thought on this one...
If the problem came back, without verify data reporting that there is something wrong, then the scenario might be somewhat different.
Our current thought is that it might be related to the fact that we scan the datebook in the background at launch time. That process might not be done yet, and would account for the slowness. Because we insist that the datebook be scanned before we do certain functions.
One way to test that theory is to start up Life Balance and do something that you expect to hit this case, then do it again. If it is faster the second time around, then that would tend to support that theory.
You might want to try purging out old datebook records. If you do that with an "archive to the PC" then you also have to do a hot sync before they really go away.
Check also that the hotsync is not a "desktop overwrites handheld" because that could undo the archive to PC stuff for the datebook records that you are trying to remove from the Palm side.
Let me know if that sounds plausible. :-)
--Catherine--*
www.llamagraphics.com
Problem is fixed
Purging old datebook records solved the problem.
Sorry for not replying earlier, but the last time I looked, I couldn't find this thread.
Thanks for the help!