snoble
asked on
Timed Triggered Reports
I am looking for some guidance before I build some automated reports. I already know how I will output/distribute the reports(s), but I am trying to understand the best way to trigger the reports. Basically I want to trigger a couple of reports to be sent out say at 6 pm every weekday night.
My db has a BE and multiple FE's distributed out. I first thought i could have a code to execute on the Current Event for the Main Form of the db to say such in the below example, but I thought of two scenarios that might not work with this idea. 1) Anyone who had the db Open when then execute possible multiple e-mails that are sent out and also I would have to ensure to keep a db Open to at least execute the code at the set time.
My idea is to create a separate FE basically to run the automated reports and keep it open at all times.
Any suggestions or different approaches to this scenario... so basically I just need a way to execute a timed event every weekday.
Example:
If Time = 6:00 pm Then
DoCmd.Output..... <- Output Reports
SendEmail <--- A Sub to distribute attached Reports to users.
End IF
My db has a BE and multiple FE's distributed out. I first thought i could have a code to execute on the Current Event for the Main Form of the db to say such in the below example, but I thought of two scenarios that might not work with this idea. 1) Anyone who had the db Open when then execute possible multiple e-mails that are sent out and also I would have to ensure to keep a db Open to at least execute the code at the set time.
My idea is to create a separate FE basically to run the automated reports and keep it open at all times.
Any suggestions or different approaches to this scenario... so basically I just need a way to execute a timed event every weekday.
Example:
If Time = 6:00 pm Then
DoCmd.Output..... <- Output Reports
SendEmail <--- A Sub to distribute attached Reports to users.
End IF
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I appreciate the code... and I figured out the scheduled tasks but since the db is on a Server and the Network Admin is a dickhead, I am sure I would have littled or no access to play with the scheduled tasks. Appreciate the advice... I will just create another FE that is always open to manage the reports.
Also... what is the bHasRun code? I am still a novice, and would like to know how to work that one. Thanx all....
Steve OUT!
Also... what is the bHasRun code? I am still a novice, and would like to know how to work that one. Thanx all....
Steve OUT!
bHasRun is just a variable that you declare in your routine.
Dim bHasRun as boolean
bHasRun = false
if ...
You don't need to set the scheduled task on the server. Make a front end that does one thing - run your reports when it opens, then it closes.
Put the front end on any machine you have access to.
Make the sched task on that machine - voila!
Dim bHasRun as boolean
bHasRun = false
if ...
You don't need to set the scheduled task on the server. Make a front end that does one thing - run your reports when it opens, then it closes.
Put the front end on any machine you have access to.
Make the sched task on that machine - voila!
ASKER
Woud like to... but we are through Terminal Services only and the bastard even locks out the right click on the damn mouse! No access to even the control panel. Will see if he would "bless" me with the permissions.
Also as a note... would I have to be logged on to have the scheduled task execute?
Also... thought the bHasRun was some cool code I hadn't seen yet. Thanks
Steve OUT!
Also as a note... would I have to be logged on to have the scheduled task execute?
Also... thought the bHasRun was some cool code I hadn't seen yet. Thanks
Steve OUT!
Yeah, you would have to be logged in for it to run.
If your Admin leaves the server logged in all the time on a particular account, that would be the account to set it up on.
Maybe he might take some comfort knowing that your program will terminate as soon as it's finished - leaving the server unencombered with more processes.
If your Admin leaves the server logged in all the time on a particular account, that would be the account to set it up on.
Maybe he might take some comfort knowing that your program will terminate as soon as it's finished - leaving the server unencombered with more processes.
ASKER
Thanx for the info.... Have a good one.
ASKER