Compiled Application vs Macro Script

Technical support and scripting issues

Moderators: JRL, Dorian (MJT support)

Post Reply
vvkozmenko
Newbie
Posts: 1
Joined: Tue Jan 22, 2008 4:48 pm

Compiled Application vs Macro Script

Post by vvkozmenko » Tue Jan 22, 2008 9:22 pm

Hi,
I have a problem that I need help with. I have written several macros that perfectly do their job when they are run from within MacroScheduler 9.2. When I compile them into standalone applications they fail to perform correctly.
What is the problem? What am I missin?
Thank you.
Val
vvkozmenko

User avatar
JRL
Automation Wizard
Posts: 3532
Joined: Mon Jan 10, 2005 6:22 pm
Location: Iowa

Post by JRL » Tue Jan 22, 2008 9:51 pm

Most likely culprit is timing. Compiled macros run more efficiently so they might be working faster. Another possibility is that you compiled these to use on another computer. Timing on different computers will rarely be identical.

Try to eliminate static waits (Wait>2) and replace them with logical waits such as WaitWindowOpen> or WaitReady>.

This topic has been discussed at length on the forum.

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

Post by Me_again » Tue Jan 22, 2008 9:56 pm

If the macro accesses/writes files be sure you have the directory paths defined or use the directory variables.

Please post the code then we can help.

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