Error: Cannot create file "C:\Program Files....\_debug.

Technical support and scripting issues

Moderators: Dorian (MJT support), JRL

Post Reply
rasmon
Newbie
Posts: 2
Joined: Wed May 26, 2004 8:36 pm

Error: Cannot create file "C:\Program Files....\_debug.

Post by rasmon » Wed May 26, 2004 8:48 pm

I am getting an error when I try to run any macro from the Editor. How can I get around this problem?

The error is:
Cannot crate file "C:\Program Files\MJT Net Ltd\Macro Scheduler\_debug.dbg". The process cannot access the file because it is being used by another process.

Thanks!

armsys
Automation Wizard
Posts: 1108
Joined: Wed Dec 04, 2002 10:28 am
Location: Hong Kong

Post by armsys » Fri May 28, 2004 2:21 am

rasmon,

Most likely _debug.dbg was corrupted by accident. Just follow the simple steps:
1. Quit from Macro Scheduler.
2. Delete C:\Program Files\MJT Net Ltd\Macro Scheduler\_debug.dbg.
3. Run Macor Scheduler again.

Happy scripting.

rasmon
Newbie
Posts: 2
Joined: Wed May 26, 2004 8:36 pm

Post by rasmon » Fri May 28, 2004 4:32 pm

Worked like a charm. Thanks Armstrong!

-- Rasmon

Guest

Post by Guest » Wed Jun 23, 2004 4:43 pm

armsys wrote:rasmon,

Most likely _debug.dbg was corrupted by accident. Just follow the simple steps:
1. Quit from Macro Scheduler.
2. Delete C:\Program Files\MJT Net Ltd\Macro Scheduler\_debug.dbg.
3. Run Macor Scheduler again.

Happy scripting.
Mine repeatedly corrupts _debug.dbg when I try to step through a WaitWindowOpen command. Or when I try from the editor to run a macro that contains a WaitWindowOpen command. I see there's a "refocus windows" option, which I have checked, but I don't know what it does.

Any suggestions?

Chris

Guest

Post by Guest » Wed Jun 23, 2004 5:28 pm


Mine repeatedly corrupts _debug.dbg when I try to step through a WaitWindowOpen command. Or when I try from the editor to run a macro that contains a WaitWindowOpen command. I see there's a "refocus windows" option, which I have checked, but I don't know what it does.

Any suggestions?

Chris
Okay, found the help file on the debugger-- so is the debugger just not meant to debug focus changes? Also, is there a way to run the entire macro without closing the editor window? The debugger just hangs when we click "run" from the debug window.

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