[AccessD] Solution in search of a problem and a problem in search ofa solution

IIRC you can pass in a macro name to run when you start Access.  Pass in a macro name when you fire 
it up from the scheduler which sets a variable etc.

http://support.microsoft.com/kb/209207

Notice the /X macro

John W. Colby
www.ColbyConsulting.com

On 11/17/2010 10:55 AM, Rocky Smolin wrote:
>
>
> -----Original Message-----
> From: dba-ot-bounces at databaseadvisors.com
> [mailto:dba-ot-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
> Sent: Wednesday, November 17, 2010 7:41 AM
> To: 'Off Topic'
> Subject: [dba-OT] Solution in search of a problem and a problem in search
> ofa solution
>
> Dear List:
>
> I am instructing my client to use the windows task scheduler to give them
> the ability to run a couple of long calculations overnight.  The program
> that will be run is a stripped down version of my manufacturing software
> which will run the cost roll-up and MRP calculations. I call it
> Autorun_Calcs.
>
> Solution to a problem: When I tried to schedule it I got an access denied
> error from the scheduler wizard; hotfix on the Microsoft site was for
> pre-SP3 and wasn't needed. Another thread however, suggested that the
> administrator user needed a password.  I don't put passwords on my admin
> user account because it's just me here and the PW is a PITA.  So I added a
> password to the admin account, set the password in the scheduled task and
> viola! it ran.
>
> Problem looking for solution: The app supports multiple back ends.  So the
> user needs to be able to change back end in Autorun_Calcs to point to the
> back end that they want to run the calcs on.  So when the program starts it
> needs to know if the user wants to NOT run the calcs but go to the utility
> menu where they can relink to a different back end.  Is there some clever
> trick by which the program can 'know' if it was started by the user or by
> the task scheduler?
>
>
>
> MTIA
>
> Rocky
>
>
>
>