Problem with MACRO command

Technical support and scripting issues

Moderators: JRL, Dorian (MJT support)

Post Reply
User avatar
pgriffin
Automation Wizard
Posts: 460
Joined: Wed Apr 06, 2005 5:56 pm
Location: US and Europe

Problem with MACRO command

Post by pgriffin » Fri Jul 29, 2005 3:51 am

I have a Macro which sets up an application for the days processing, then calls the macro which actually does the work all day. For no apparent reason, the second macro does not seem to be starting anymore.

I have not upgraded anything,
I have included the full path in the Macro> command,
when I run the second macro manually, it starts fine and runs all day long.

For now, I have put them on seperate schedules. the first macro runs at 6:30 a.m. the second macro runs at 6:35.

very puzzled.

SkunkWorks

User avatar
Bob Hansen
Automation Wizard
Posts: 2475
Joined: Tue Sep 24, 2002 3:47 am
Location: Salem, New Hampshire, US
Contact:

Post by Bob Hansen » Fri Jul 29, 2005 7:27 am

Please provide the code that calls the macro so we can look at it.
Any variables to be passed from macro1 to macro2?
Hope this was helpful..................good luck,
Bob
A humble man and PROUD of it!

User avatar
pgriffin
Automation Wizard
Posts: 460
Joined: Wed Apr 06, 2005 5:56 pm
Location: US and Europe

Post by pgriffin » Fri Jul 29, 2005 5:08 pm

macro>C:\Program Files\MJT Net Ltd\Macro Scheduler\EssickShipAgainstOrders.scp

and that is the correct path

User avatar
pgriffin
Automation Wizard
Posts: 460
Joined: Wed Apr 06, 2005 5:56 pm
Location: US and Europe

Post by pgriffin » Fri Jul 29, 2005 5:40 pm

AHA! Macro> cannot call macros which are encrypted, even if you do not specify "require password to run". The macro still will not run. I would like to encrypt, but ...

why isn't this in the help files?

SkunkWorks

Me_again
Automation Wizard
Posts: 1101
Joined: Fri Jan 07, 2005 5:55 pm
Location: Somewhere else on the planet

Post by Me_again » Fri Jul 29, 2005 8:42 pm

SkunkWorks wrote:AHA! Macro> cannot call macros which are encrypted, even if you do not specify "require password to run". The macro still will not run. I would like to encrypt, but ...

why isn't this in the help files?

SkunkWorks
How about compiling it to an .exe and calling that instead?

Post Reply
Sign up to our newsletter for free automation tips, tricks & discounts