Clock v1.2

[rafgoor]

Hi,

with release3 came the program 'Clock v1.2'. Instead of giving only the date and the hour, it actually gives you also the possibility to set up an alarm, and it should give the 'Next appointment Today'.
However, even with an appointment set in my Date Book (with or without the alarm on), the 'Next Appointment Today' says always 'None Found'.

What do I wrong or is this a bug?

Regards

[sPo-One]

Strange, mine works just fine.
It displays my next appointment.

[apersson850]

A beta version behaved like that, if the datebook was open when invoking the clock. But that should have been fixed in the final release.

[rafgoor]

Date Book open or not, Clock returns always 'None Found'.

My date Book is version 4.52G.

[sPo-One]

So is mine...

[apersson850]

It had nothing to do with the version of the Datebook program itself. It was the clock program, which accidentially opened the Datebook DB in the wrong mode, so it wasn't reachable, if it already was open by another application. Most likely the Date Book, or, like in my case, DateBK5.

[Bavarian]

Originally posted by rafgoor
with release3 came the program 'Clock v1.2'. Instead of giving only the date and the hour, it actually gives you also the possibility to set up an alarm, and it should give the 'Next appointment Today'.
However, even with an appointment set in my Date Book (with or without the alarm on), the 'Next Appointment Today' says always 'None Found'.


Search for appointment and you find the following thread:

http://www.pdastreet.com/forums/showthread.php?s=&threadid=38340&highlight=apointment

[rafgoor]

Mike,

Thank you for the link. Probably there is a problem with the database of my Date Book. I know I may not do it, but at work, I sync on a Windows NT PC with Outlook, but sometimes, at home, I sync (iQue overwrites everything, if I don't forget to control my settings) on a OS9 Macintosh with Entourage.

This is asking for trouble, I know, but ...

Vielen dank

[Bavarian]

I think it is a trouble with a database generated before R3! After updating to R3 i discoveed the problem. When i generated a new database with the same entries by hand, the problem was gone. At this time i had only about 30 entries - so it was not too much pain to enter all again by hand.