There are two ways you can do it.

First, you can physically add the recurring birthday events to your EventT. For example, you could have code run when the database opens, perhaps once a week, that looks ahead and creates any needed birthday events for the coming year. Or, when you first add a person, you could automatically generate the next 50 birthdays.

That works, but remember that if you later change the person's name, birth date, or anything else, you have to update all of those generated events too.

The method I would probably use is to add a Yes/No field to your EventT, something like IsRecurring. Store the birthday event once, mark it as recurring, and have the calendar's query/code look for recurring events and display them every year. It takes a little more work in the calendar logic, but you only have one record to maintain. Change the person's information once, and all future calendar displays are automatically correct.

I covered some different methods in my Next Appointment video. It deals with recurring appointments, but it's the same logic, whether it's birthdays, anniversaries, whatever.

thanks Richard

I will take a look.