msgbox reminder every 25th

  • Thread starter Thread starter Joe Smith
  • Start date Start date
J

Joe Smith

Hello,

I need a msgbox to popup every 25th of the month as a reminder to
reorder a certain product. I tried doing this with the msgbox macro
option with condition: day(date())=25. But it doesn't seem to work.
Could someone please help me with this? Thank you very much in advance.
 
SQL Server can run a batch on the 25th of every month. This is
available via SQL Agent.

MS Access just flat out doesn't have this functionality
 
Hello,

I need a msgbox to popup every 25th of the month as a reminder to
reorder a certain product. I tried doing this with the msgbox macro
option with condition: day(date())=25. But it doesn't seem to work.
Could someone please help me with this? Thank you very much in advance.
Click to expand...

Two important questions:
1. Is your database running everyday?
2. If so, is there a form open?


Assuming your database has an open form whenever the database opens,
then...
If your database is always open (24/7), then your code should work if
it is used in the timer event of the form.
If your database is not always open, but opened at least once
everyday, then your code should work if it is used in the open event
of the form.

Fred
 
a a r o n . k e m p f @ g m a i l . c o m said:
SQL Server can run a batch on the 25th of every
month. This is available via SQL Agent.
Click to expand...

So what? The poster asked about running a particular Access application, not
about SQL Server. Can SQL Server run the Original Poster's Access
application via SQL Agent? I didn't think so.
MS Access just flat out doesn't have this functionality
Click to expand...

Zuckerman told him how, exactly, under two scenarios.

A third, of course, would be to use Windows scheduler to start his Access
application on the 25th of each month, and use an AutoExec macro or VBA
startup code to perform the desired action.

You demonstrate again that you know little about SQL Server and even less
about Access, and that your primary purpose in this newsgroup is to mislead
those who seek usable information.

Larry Linson
 
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
 
SQL Server has SCHEDULING CAPABILITIES.. and Access just doens't have
this functionality.

Use the right tool for the job!
 
Aaron, SQL server has nothing to do with the question of the poster. He is trying to inform the logged in user of a condition. He is NOT trying to run a batch job. My recommendation would be the same REGARDLESS of what back end database he was using and in fact - nothing in the post tells us whether the poster is using SQL Server, DB2, Oracle, or Jet/ACE nor is the back end relevent.

Submitted via EggHeadCafe
Microsoft SQL Server DBA For Beginners
http://www.eggheadcafe.com/training-topic-area/SQL-Server-DBA/6/SQL-Server-DBA.aspx
 
Pat;

Eat shit lamer. Just because you're stuck using an obsolete database,
that doesn't mean that I'm out of line for reccomending that they use
the RIGHT tool for the job.

SQL Server is an optional backend engine for MS Access, it is all
about 'Access Data Projects'

-Aaron
 
a a r o n . k e m p f @ g m a i l . c o m said:
SQL Server is an optional backend
engine for MS Access, it is all
about 'Access Data Projects'
Click to expand...

ADPs are not even the recommended approach to using SQL Server backends
anymore, but, hey, for a "DBA" stuck back at the 2005 level, what kind of
advice could we suspect -- particularly one who doesn't keep up on Access
any better than he keeps up on SQL Server.

And _he_ has the gall to call Pat Hartman, who definitely knows what's up, a
"lamer". Ha, I bet Pat's never spent time in the slammer, nor been
permanently recorded in official court records * as having confessed to
stalking, either.

* as has been cited, several times, with links to
Washington State court records, for a a r o n

Larry
 
"a a r o n . k e m p f @ g m a i l . c o m" <[email protected]>
wrote in
:
SQL Server can run a batch on the 25th of every month. This is
available via SQL Agent.

MS Access just flat out doesn't have this functionality
Click to expand...

Neither does SQL Server Express, which doesn't include the SQL
Server Agent.

But you can easily write VBScripts and schedule them in the Windows
Task Manager to do Access/Jet/ACE-related tasks. Those can be as
simple or as complex as needed (i.e., just use DAO to operate on
data, or automate all of Access in order to do things that require
the Access UI, like send reports to PDF; though naturally, those
latter things must be run within a logged on session). Why should
Access need task scheduling built into it when the OS provides that
functionality already?

You really don't know anything at all. If you did, your objections
to Access wouldn't be so incredibly lame.
 
This is not your personal classified advertisement newsgroup, Andrej. If you
feel compelled to seek employment via the Internet, at least have the
courtesy to other participants to send your solicitations via e-mail,
instead of cluttering the newsgroups.

Most everyone here knows that there is so much scamming, identity theft, and
virus and worm spreading going on that they aren't likely to respond to an
unsolicited offer from an unknown party. (And, if they didn't, after reading
this, they should be that cautious.)

Larry Linson
Microsoft Office Access MVP
 
Larry;

that's cute dude.. of course, it never happened.. I never plead to
anything.. was never found guilty, etc

Anyone using Access as a DATABASE should be fired and then spit upon.
Access is great for forms.. Access Reports are obsolete (Because SQL
Server Reporting Services is free and much better)

-Aaron
 
this is the internet. people are free to solicit work-- just like MVPs
solicit work and get paid for their work.

your double standard is stupid.

Learn a current database, and then maybe you can make six figures as
well!

-Aaron
 
wow. you actually trust the windows scheduler?

SQL Server scheduling capabilities are 10000 times more powerful than
the AT scheduler

-Aaron
 
Back
Top