_Dump_Vars help Please

PepsiHog · Post by **PepsiHog** » Sat Aug 04, 2012 12:03 am

Hello Eveyone,

Does anyone know how to use _Dump_Vars? I'm searching for the log file but can't seem to locate it.

Please help. Thanks.

PepsiHog

Post by **Marcus Tettmar** » Mon Aug 06, 2012 6:24 pm

Let>_DUMP_VARS=1

All variables will now be output to log file until ...

Let>_DUMP_VARS=0

PepsiHog · Post by **PepsiHog** » Tue Aug 07, 2012 12:21 am

@Marcus

OK. I did that and could not find the log file. Where is the log file written?
I am running version 12.1.10.

Thanks for helping,
PepsiHog

JRL · Post by **JRL** » Tue Aug 07, 2012 3:40 am

Go to help and search for "logging". You must enable logging and with every method of enabling logging you will specify the log file name.

PepsiHog · Post by **PepsiHog** » Tue Aug 07, 2012 10:45 pm

Thanks JRL.

I tend to only use the editor. I don't have MS loading at startup. And it never occured to me to look at the main menu. (out of sight, out of mind)

@ Marcus,

My bad for not looking at the main, but may I suggest a link being added to System Variables under _Dump_Var for logging?

Is there any way of placing a shortcut on my desktop to run the editor that has all the tabs? Why does the stand alone editor exclude all these options? I tend to only use the stand alone editor. So if I want to use logging I have to run and use the main?

Anywho,
PepsiHog

PepsiHog · Post by **PepsiHog** » Tue Aug 07, 2012 11:29 pm

Here is what I did.

1) I ran the main menu for MS.
2) I clicked the tab Logging.
3) I clicked Browse.
4) I entered a name. (Macro_Log)
5) I click the tab Script.
6) I loaded my macro.
7) I added the line Let>_Dump_Vars=1
8) I ran the macro.

It ran slow. To be expected. But no log file. I browsed to the desktop in step 3. So the file should have been on the desktop. Nop.

Did I miss something?....

Thanks,
PepsiHog

PepsiHog · Post by **PepsiHog** » Thu Aug 16, 2012 5:33 pm

Test reply. Ignore this.

PepsiHog · Post by **PepsiHog** » Tue Aug 21, 2012 1:46 pm

I guess everyone is busy with version 13.......................................

Rain · Post by **Rain** » Tue Aug 21, 2012 2:01 pm

Hi PepsiHog,
I don't run Windows XP but I have versions 12 and 13. I was able to log a macro with version 12.

Try the following:

1. Create a log file on your desktop. (I created a txt file and named it MS Log)

2. Browser to the log file you created and select it.

3. Select the log level.

4. Close the Macro editor window and click save.

5. Run the macro.

6. Open the log file.

I hope this helps.

PepsiHog · Post by **PepsiHog** » Tue Aug 21, 2012 5:18 pm

Thanks, Rain. But I did as you suggested and still nothing. The txt file remains empty.

Just by chance, what version of 12 do you have? I have 12.1.10.

What extention does a log file have? I tried .log but that didn't work.

Rain · Post by **Rain** » Tue Aug 21, 2012 5:37 pm

12.1.10 as well and I log to a regular text file (.txt)

Maybe your antivirus or spyware programs are having a problem with Macro Scheduler creating a log? Have you tried disabling everything i.e Firewall, antivirus, adware or spyware protection programs and then using the log feature?

PepsiHog · Post by **PepsiHog** » Tue Aug 21, 2012 6:13 pm

LOL. This is sad, but I have to admit it's also comical!

Thanks, Rain.

I closed all. Virus and everything else. But nothing.

However, atleast I know that it should work now. My next step is to restore an image of Win XP that has nothing installed. Install MS and give it another go.

I even went into notepad and saved it from there. I made the filename "Simple.txt" and then selected it from the browse in logging. I'm even using a shorter script. Just in case the original is so long it's having a fit. But nop.

Oh, yeah. I even went so far as to install MS 12.1.6. That's before your last post.

I may not have had any success, but thanks, because you have helped with the info.

Post by **Marcus Tettmar** » Tue Aug 21, 2012 7:09 pm

PepsiHog wrote:Is there any way of placing a shortcut on my desktop to run the editor that has all the tabs? Why does the stand alone editor exclude all these options? I tend to only use the stand alone editor. So if I want to use logging I have to run and use the main?

Because those tabs are related to the properties of macros stored and maintained within Macro Scheduler. The scheduler, hot key/event trigger handler and so on are all maintained and managed by Macro Scheduler. None of those things are stored in the script file. Outside of Macro Scheduler, in the script editor, these things have no context.

The standalone editor is exactly that - standalone - it is just a text editor. It knows nothing about what is set up inside Macro Scheduler. When you run the standalone editor you are not doing anything inside of Macro Scheduler you are plainly and simply editing a text file (a .scp file). Even if that .scp file just happens to be one that is linked to a macro inside Macro Scheduler, the editor doesn't know about that link.

You can still use logging with external scripts. You would have to run the script via the command line with /LOGFILE=c:\bla\somelog.txt on the command line. This is then totally independent of settings within Macro Scheduler (remember the .scp file you are editing may not even exist within Macro Scheduler).

Logging has no effect when you are running a script in the debugger (editor), whether using the internal or external standalone editor.

I suspect you are expecting the log file to be generated while you are in debug mode, or running the .scp file outside of Macro Scheduler. That won't happen.

If you have gone into Macro Scheduler, edited the properties of a macro and added logging, the log file will only be created/updated when you CLOSE the macro properties and run the macro within Macro Scheduler.

If you run a script file standalone (as a .scp outside of Macro Scheduler, rather than via a macro setup inside) then you'd need to specify a log file on the command line.

PepsiHog · Post by **PepsiHog** » Tue Aug 21, 2012 9:30 pm

Marcus,

You hit the nail on the head. I was running the script from the editor with all the tabs.

You have to run the script in MS main window, without opening the script for editing.

Case closed.

Thank you.
PepsiHog

I see now that Rain specified that in his directions. Sorry. I was so focused on doing it in the editor that I didn't realize the meaning. I think the nice way is to say I had a senior moment. *For an extended length of time.

Sure glad I didn't restore Windows! That's the GOOD news! LOL to infinity and beyond!

Thank you, Rain.
Thank you, Marcus.