macro not working?
Moderators: JRL, Dorian (MJT support)
macro not working?
the auto was working with the macro scheduler, and all of the sudden it stopped working, could it be because I need to purchase it, or could it be another problem, it just stopped working...?
- Bob Hansen
- Automation Wizard
- Posts: 2475
- Joined: Tue Sep 24, 2002 3:47 am
- Location: Salem, New Hampshire, US
- Contact:
What is the auto? This is a foreign term. Do you mean it was scheduled to run on a certain date/time? Run by itself if a certain window opened up? Run by itself when logging in to the system?the auto was working
Troubleshooting:
Did you make a log, and review the log contents?
Did you single step through the lines looking at values of variables?
Have you inserted messages to report conditions at progressive steps?
Hope this was helpful..................good luck,
Bob
A humble man and PROUD of it!
Bob
A humble man and PROUD of it!
Have you disabled scheduling? Is the software running continuously? What does it say under macro properties / run when?
MJT Net Support
[email protected]
[email protected]
macro stopped working automatically...
I haven't changed any of the settings, everything was working right, automatically working, and then one day I clicked on macro under programs, and hit run now, like always, and it worked, then stopped, wasn't auto like before... ???
macro not working...
Under run when, it still says repeat continuously like before, I haven't changed anything, could it be because my 30 day free trial is up? Could that be why it's not automatically running continuous anymore?Thanks
Could you provide any code?
Something like "yesterday my grandma was still alive, we haven't changed anything, what has happend" won't help us to help you.
It could be something tiny like a Wait> which had worked for a billion times, but is to short now, or a window has changed its title and there's a WaitWindowChanged>, or ...
So, where's the beef
Something like "yesterday my grandma was still alive, we haven't changed anything, what has happend" won't help us to help you.

It could be something tiny like a Wait> which had worked for a billion times, but is to short now, or a window has changed its title and there's a WaitWindowChanged>, or ...
So, where's the beef
