PDA

View Full Version : Palm Datebook Error on TH55...


tonyreynolds
06-01-2005, 09:41 AM
Any database gurus out there...

I get the following error message when selecting a different day at the top of the Palm Datebook day-view screen:

Table.c, Line:3186, Invalid row

I then have to reset the device by tapping the reset button on the screen.

Sometimes I get the error after one tap, sometimes after several. I never get the error in Clie Organizer, just in the Palm Datebook.

I downloaded a old Pimlico applet that's supposed to find and correct datebook errors, but it never finds anything wrong.

I have tried purging all items more than a week old, same error.

I have tried deleting the Datebook databases and restoring from a backup, same error.

The last time I did a hard reset (a couple months ago...), the Datebook worked fine and then the same error starts back up again.

Any ideas?

Do CO and Datebook share the same database, or do they just look to each other for compliance?

Tony :(

tonyreynolds
06-03-2005, 11:10 AM
I'm wondering if this could be something with Clie Organizer and Palm Datebook trying to share data and the data being corrupted in any way.

Has anyone else had this error message?

Do I call Palm or do I call Sony?

Any input would be greatly appreciated, because at this point, I'm about ready to give up on Datebook and just use CO exclusively...

Tony

tonyreynolds
06-03-2005, 11:36 PM
Since no one seems to know what the problem might be with the Palm Datebook, I've decided just to not use it. It was crashing my TH55 every time I tried to access a different day.

I've assigned Clie Organizer to my Datebook button, and ya know, the more I use it, the more I like it...

:)

depret
06-04-2005, 06:54 AM
Just remember ...

http://www.1src.com/forums/showpost.php?p=530884&postcount=1

tonyreynolds
06-04-2005, 10:52 AM
Just remember ...

http://www.1src.com/forums/showpost.php?p=530884&postcount=1

Thanks for the memories....

I've never had the problem that the link refers to, namely an alarm freeze. It could be because I use Fons4OS5 and DON'T use a small font.

I'm pretty certain I know "about" where the problem lies with Palm Datebook: Somewhere it's getting a corrupt entry, but I don't have the time to track it down. I was able to get it working afew months ago when this problem cropped up, but it's come back with a vengence, and this time I have no patience for it.

BTW, I am running the latest version of CO (1.02) which was released after rldunn had his alarm problem.

TR