Since the 25th of the month can fall on any day of the week, you can't be certain that someone will open the database on that date. The most precise way would be to keep a log of orders placed. Then, each time the application opens, your opening form would look up the last order date and determine if the order was placed on time. If it was not, you would display a messge box to notify the user. With this method, the warning would happen for each user, each time they open the app until the order was placed.
If you can't create log records for the order process, you should create log messages for the warning. Again, your code would run in the open event of the start up form. But this time it would look for a "message sent" date. If the message was not sent, you would log the message and display the message box. Otherwise, you would just continue with your normal processing.
If you don't want to log either the order or the message event, you would still display the message box from the open event of your start up form. This time, you would check the date and if it was the 25th display the message. To handle the months when the 25th falls on the weekend, you would have to determine which day of the week the 25th fell on and display the message the following monday.
Of course, the simplest solution is to just check the date and display the message if the date is the 25th. Here, you run the risk of forgetting to place the order because the database wasn't opened on the 25th. You also may annoy the users because every one of them will get the message every time they open the app on the 25th.
Submitted via EggHeadCafe
Microsoft LINQ Query Samples For Beginners
http://www.eggheadcafe.com/training...erators/33/LINQ-Standard-Query-Operators.aspx