When using Macro> in 7.4.004 it still looks for the macro script in c:\program files\mjt.... instead of the new path for the Ms data folder (e:\my documents\macro scheduler).
If I use the full path e.g. macro>e:\my d.... it just thinks that is the full macro name and returns cannot find c:\progr....\e:\my doc...
I do not have .scp files associated in windows in order for me to easily edit with notepad, so run program or execute file is unlikely to work as a macro either.
If I leave all my old macros in c:\prog..., the macro> will work, but of course updating all macros in editor is editing the ones in the new folder at e:\my doc.. so if i update the macro called with macro>, it always uses a very old one left in c:\prog as opposed to the updated one in e:\.
so in summary, macro> points to any macros founf in c:\prog, but editor edits and saves in the folder specifed during installation (e:\my doc..)
Any ideas?
macro> incorrect path in 7.4.004
Moderators: JRL, Dorian (MJT support)
- Dorian (MJT support)
- Automation Wizard
- Posts: 1417
- Joined: Sun Nov 03, 2002 3:19 am
You should always put a path in the Macro> command. This has been the case since 7.1. Without a path it will look in the program directory. If your macros are in the same directory get into the habit of doing this:
Macro>%SCRIPT_DIR%\scriptfile.scp
Macro>%SCRIPT_DIR%\scriptfile.scp
MJT Net Support
[email protected]
[email protected]
The help file for the Macro function states that is advisable to use the full path for your macro name. I thought that maybe you would need quotes around the path and filename if there were spaces in your path. I found that this is not the case, in fact putting quotes around the path and filename gave me a macro not found error.
You do not show quotes around the snippets of path\filename that you posted, but I thought it might be worth asking if you had quotes around them in the macro> line?
Hope this helps,
Dick
You do not show quotes around the snippets of path\filename that you posted, but I thought it might be worth asking if you had quotes around them in the macro> line?
Hope this helps,
Dick
- Dorian (MJT support)
- Automation Wizard
- Posts: 1417
- Joined: Sun Nov 03, 2002 3:19 am
Thanks for the quick reply.
if i used the full path, e.g. macro>e:\my doc.... i'd get macro not found error because it was looking in c:\my prog...mjt\e:\my doc..\macroname.scp
%SCRIPT_DIR%\macroname.scp seems to work nicely.
now i just have to figure out why the alt key no longer seems to work to bring up the menu in editor, so i can't type alt fs to save the file. maybe a rebbot and we'll see what happens.
if i used the full path, e.g. macro>e:\my doc.... i'd get macro not found error because it was looking in c:\my prog...mjt\e:\my doc..\macroname.scp
%SCRIPT_DIR%\macroname.scp seems to work nicely.
now i just have to figure out why the alt key no longer seems to work to bring up the menu in editor, so i can't type alt fs to save the file. maybe a rebbot and we'll see what happens.
Sounds like you had not included the extension - .scp. Since 7.1 you should always include the full path and extension.
No idea why ALT-S in editor isn't working. Ok here. Let us know if it persists.
No idea why ALT-S in editor isn't working. Ok here. Let us know if it persists.
MJT Net Support
[email protected]
[email protected]
-
- Newbie
- Posts: 4
- Joined: Tue Feb 13, 2007 12:16 am
Macr> broken in 8.1?
Don't forget the extension must be included .scp