Gosh, darn, lost my work again!

Me_again · Post by **Me_again** » Mon Feb 07, 2005 7:03 pm

I can't handle the little window so I like to work in the editor. Seems that even though I continually use the save button, if my macro loops/becomes unresponsive and I can't exit normally, then the work isn't actually saved anywhere (at least not under the macroname). Apart from writing bad macros am I doing something wrong?

support · Post by **support** » Mon Feb 07, 2005 7:08 pm

Well since it is possible that a badly written macro could cause a crash or a tight loop you would be well advised to save the macro and close it before attempting to run it/debug it. If you open it up directly in the editor just saving it should be fine before running it.

Me_again · Post by **Me_again** » Mon Feb 07, 2005 7:27 pm

What I'm saying is that if I
Start MS
Show
Right click my macro
Edit Script
Make a change
Click the floppy button, or do file save, it doesn't actually save the changes in the macroname.scp file on the disk.

It only appears to update the .scp file if I choose save when closing the editor.

If closing the editor is the only way to save before a test run, why have the floppy button or file save on the file menu?

Me_again · Post by **Me_again** » Mon Feb 07, 2005 7:44 pm

What I'm saying is that if I
Start MS
Show
Right click my macro
Edit Script
Make a change
Click the floppy button, or do file save, it doesn't actually save the changes in the macroname.scp file on the disk.

It only appears to update the .scp file if I choose save when closing the editor.

If closing the editor is the only way to save before a test run, why have the floppy button or file save on the file menu?

support · Post by **support** » Mon Feb 07, 2005 8:02 pm

I'll look at this again. If you open it directly in the script editor then it should save it direct to file. It won't if you open the macro properties window first, because then it will update the macro properties and won't be saved until you OK the macro properties. But, as I said, it should be saving to disk if you are opening it up direct. So I'll get it checked out for sure and if there's a bug we'll fix it.

In the mean time I would advise saving and closing after any major changes before running. When in the editor I routinely use the debugger to step through but very rarely run it whole from within the editor, preferring to save, close and then run if I am going to run the entire script. When debugging you can stop and save during the process.

Me_again · Post by **Me_again** » Mon Feb 07, 2005 8:44 pm

Thanks for looking. I have 7.3.04 Pro.

I'm doing as you suggest now and it works fine.

Guest · Post by **Guest** » Tue Feb 15, 2005 4:01 am

support wrote: So I'll get it checked out for sure and if there's a bug we'll fix it.

Works much better in the new version, many thanks again for your attention and support

Me_again · Post by **Me_again** » Tue Feb 15, 2005 4:03 am

Oops, that was me-again again