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

I think for this to work you need to include the path to the MSAccess.exe
file.  This is for Access 2003 on W7.

"C:\Program Files (x86)\Microsoft Office\OFFICE11\MSACCESS.EXE" 
"C:\Clients\E-Z-MRP23\E-Z-MRP_Autorun_Calcs.mdb" /cmd xyz

You'll need to enter the double apostrophe at the start and end of the path
to each file.

Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Wednesday, November 17, 2010 10:44 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Solution in search of a problem and a problem
insearch ofa solution

I tried triggering the program with 

C:\Clients\E-Z-MRP23\E-Z-MRP_Autorun_Calcs.mdb /cmd xyz

And in the opening form put  

MsgBox "*" & Command() & "*"

Expecting to see *xyz* but it showed only **.

I think the cmd option would be the most convenient - I recall using it
before on another app but it's not showing up here.

Rocky

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Wednesday, November 17, 2010 8:13 AM
To: Access Developers discussion and problem solving
Subject: Re: [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
>
>
>
>
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com