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.

Hi
I have created a mechanism that  uses the 'AfterUpdate' event that works off 0f  the Customers (family members) DOB and Wedding anniversary fields to create and / or modify the Calendar entries, it also works from the number of occurrances that is maintained on the Defaults Table.  

Therefore I think I have finished on this database for the time being, apart from some tidying up and new report generations.  
I currently have three forms that allow me to create a simple, a continuous and a recurring set of calendar entries - I need to change this to use a single form.


Thankyou for all your help

Alfred

p.s I have also been looking at the KanBan videos - I have some comments, if you are interested, but am not ready to send them yet.  I need to continue developing my @MyPhotography' database first.

Nice job, Alfred. That sounds like a solid solution. Using the CustomersF AfterUpdate event along with the number of occurrences from your DefaultsT gives you the automation you need while still letting you control how far ahead those events are generated.

And yes, consolidating the simple, continuous, and recurring appointment entry forms into one form is a good next cleanup project. You can use an option group or combo box to select the event type, then show only the fields that apply to that type. That will make it easier to maintain later.

Feel free to send your Kanban comments whenever you're ready. Good luck with @MyPhotography first - finishing one project before jumping too deeply into the next is usually the battle. I have that problem myself. I'll start something, get a proof of concept built, and then not finish it when all it really needs is just some touchups. I've got a whole new calendar database ready to go. It just needs some final polishing.

Now you tell me , LOL.... I have now got a single appointments form that handles single, continuous and recurring entries, just some little touches / tidying up to do.

Hi Richard,

I'm looking to do the same thing. (Adding Birthdays). This helps a lot.  Thanks