Bug: birthday bar links to the last used contact in Contacts

[Trinitylab]

Hi,

All my data is in the footnote, last Epim Pro Biz Net, Win 8.1 x64.

Here it is the bug:
1. I have Client's birthday set in his record, ie. it's repeated automatically.
2. When it comes closer, a kind of a white bar down the Calendar view appeares with the info about a given birthday.
3. I double-click on the white bar.
4. It takes me to Contacts, and directly to the last opened/used record, not to this Client's record.

Hope you fix it.
Piotr

[Trinitylab]

Hi,

Next version of the related bug.

See the pic:

The issue: the birthday as recurring event was on 11th June.
However it has been deleted, using the option "This Appointment".
Nevertheless, when you click on the day, you still see at the bottom this birthday bar. I think that it should be removed when the event is deleted. If a user deletes the very event, that logically does not want to see it in Calendar.

[Max]

1. I have Client's birthday set in his record, ie. it's repeated automatically.
2. When it comes closer, a kind of a white bar down the Calendar view appeares with the info about a given birthday.
3. I double-click on the white bar.
4. It takes me to Contacts, and directly to the last opened/used record, not to this Client's record.

Please try on 8.0 Release candidate viewtopic.php?f=1&t=21021
I could not reproduce the issue there.

Nevertheless, when you click on the day, you still see at the bottom this birthday bar. I think that it should be removed when the event is deleted. If a user deletes the very event, that logically does not want to see it in Calendar.

Birthday bar is tied to a birthday day in Contacts and can not be deleted without removing Birthday from Contacts. But you suggestion noted, thanks!

[Trinitylab]

Birthday bar is tied to a birthday day in Contacts and can not be deleted without removing Birthday from Contacts.

This is actually a secondary issue, can stay, as it is.

Regarding 8.0. Dear Max, cannot do that, I do not want to destroy DB (just in case).
Today it would be a real legal problem to send it to you for a fix.

[Max]

Regarding 8.0. Dear Max, cannot do that, I do not want to destroy DB (just in case).

You can make a copy of database and try there. This way you will know if the problem will be fixed in 8.0 Release.