Reminder DB: Table Structure?

P

(PeteCresswell)

Some of my guys have asked for a "reminder" database.

Did due diligence in trying to convince them to use MS Outlook...
but no-go.

First thing I did was to flip open my Palm Pilot and look at
DateBk5's functionality.

What I saw was:
------------------------------------------------------------
- Regular appointments (Name/Date/Description)

- Repeating Appointments (every N days/weeks/months/years or
irregular schedule)

- Floating appointments - that keep popping every day from the
first alert time/date until the user dismisses them
------------------------------------------------------------

Googled a little but nothing jumped out at me table-design-wise.

My kneejerk for the skeleton is:

tblAppointment
tblAppointmentDate

where multiple tblAppointmentDate records are spawned/deleted
when the user edit's an appointment's "Repeating" aspect.


Anybody been here?

Gotchas?

Sample structures?
 
Top