I go with a different logic:
I load all active reminders into a list, and use a timer in my program to go through the list once every minute.

Since some users are connecting through the Internet, I can't afford to make a query every minute to the DB.

----- Original Message -----
From: Woody
To: firebird-support@yahoogroups.com
Sent: Friday, November 19, 2010 6:19 PM
Subject: Re: [firebird-support] DB design best practices - whichsolutionisfaster?



From: "Zd" <toldy007@...>
> Hello!
>
> I'm also not sure that I understand what you say, but imagine this:
>
> If I search for reminders only AFTER a certain date, I won't be able to
> show reminders that might occur before that date.
>
> If I don't login to the program for two weeks and I miss a bunch of
> reminders, I want the program to warn me afterwards...
>

Reminders should be flagged as having been given when they occur. Your query
would take this into account.

For example:

Where (Reminder_Date_Time <= Current_Date_Time) AND (Reminder_Flag = false)

Once the reminder is displayed, the flag would be set to indicate that it
was already presented to the user so it isn't displayed again. No matter how
long it takes for you to check your schedule, the reminder would display.
However, if the event has already happened, showing a reminder would be
mute, IMO.

Woody (TMW)






[Non-text portions of this message have been removed]