Samrae

Sebastian, As was mentioned above you could use Macro Express commands to copy all files and folders in the Data folder to another folder. This example copies the files and folders from the folder Data to a folder that contains the date, e.g. E:\Data --> E:\Data09092021 while leaving the original Data folder intact. Variable Set String %SourceDir% to "E:\Data" Variable Set From File date Variable Set String %DestinationDir% to "E:\Data%FolderDay%%FolderMonth%%FolderYear%" Copy File/Files: "%SourceDir%\*.*" to "%DestinationDir%" <VARIABLE SET STRING Option="\x00" Destination="%SourceDir%" Value="E:\\Data" NoEmbeddedVars="FALSE"/> <VARIABLE SET FROM FILE Filename="%SourceDir%" Option="\x00" Date="\x01" Month="%FolderMonth%" Day="%FolderDay%" Year="%FolderYear%" Flags="\x07"/> <VARIABLE SET STRING Option="\x00" Destination="%DestinationDir%" Value="E:\\Data%FolderDay%%FolderMonth%%FolderYear%" NoEmbeddedVars="FALSE"/> <COPY FILE/FILES Source="%SourceDir%\\*.*" Dest="%DestinationDir%" Progress="TRUE" Recurse="TRUE"/> If you want to rename the Data folder you can use the following. This example moves the files and folders from the folder Data to a folder that contains the date, e.g. E:\Data --> E:\Data09092021 . The original folder E:\Data is removed. Variable Set String %SourceDir% to "E:\Data" Variable Set From File date Variable Set String %DestinationDir% to "E:\Data%FolderDay%%FolderMonth%%FolderYear%" Rename File/Files: "%SourceDir%" to "%DestinationDir%" <VARIABLE SET STRING Option="\x00" Destination="%SourceDir%" Value="E:\\Data" NoEmbeddedVars="FALSE"/> <VARIABLE SET FROM FILE Filename="%SourceDir%" Option="\x00" Date="\x01" Month="%FolderMonth%" Day="%FolderDay%" Year="%FolderYear%" Flags="\x07"/> <VARIABLE SET STRING Option="\x00" Destination="%DestinationDir%" Value="E:\\Data%FolderDay%%FolderMonth%%FolderYear%" NoEmbeddedVars="FALSE"/> <RENAME FILE/FILES Source="%SourceDir%" Dest="%DestinationDir%" Progress="FALSE" Recurse="FALSE"/> NOTE: the folder names cannot have a trailing "\" or contain "\*.*" When they do the copy or rename does not work correctly. I used the folder's modified date to create a destination folder like E:\Data09092021. I did not include hours and minutes in the destination folder name. You can easily add these. You could also choose to use the date/time when the macro runs, similar to what you have above.

There is a Scheduled Macro option to run "When the program starts". This may do what you need. If not you can use Windows Task Scheduler along with the Macro Express command line options to run a macro. The command line would look something like either of these: "c:\Program Files (x86)\Macro Express Pro 6\MeProc.exe" /A::Filename?Macroname "c:\Program Files (x86)\Macro Express Pro 6\MeProc.exe" /A:Macroname

If you have the Wait for sound to finish in the Sound Wave File command checked then you cannot stop the sound. Maybe you could try unchecking that and putting a delay after the Sound Wave File command. Then if you click to stop the delay the sound will stop.

Is Macro Express Pro running as Administrator on your Windows 10 computer? If so you could try running as non-admin.

I could not get a batch file containing any of these to work: start C:\Program Files (x86)\Macro Express Pro\MeProc.exe /APosteingang start "C:\Program Files (x86)\Macro Express Pro\MeProc.exe /APosteingang" start "C:\Program Files (x86)\Macro Express Pro\MeProc.exe" /APosteingang But a batch file containing this worked on both Windows 7 and Windows 10: "C:\Program Files (x86)\Macro Express Pro\MeProc.exe" /APosteingang I expect the parameter in Dragon should look like this but I do not have Dragon to try it: ShellExecute "C:\Program Files (x86)\Macro Express Pro\MeProc.exe" /APosteingang Have you considered upgrading to Macro Express Pro 6? Maybe it contains a change that would help.

You can still use Text File Process to loop through the text. Each line of a text file used by Windows ends with CR followed by LF referred to as CRLF. The Text File Begin/End process reads a line of text up to the CRLF. For convenience in your macro the string read by Text File Process does not include the CRLF. However, in your case, you know that each line originally had the CRLF. So, to determine the number of CRLF's just count the lines. Something like this: Variable Set Integer %N99% to 0 Text File Begin Process: "ansisavedcopy.txt" Variable Modify Integer: Inc (%N99%) // If the line is empty then stop the Text File loop If Variable %T1% = "" Break End If Text File End Process // Here: %N99% contains the number of times through the loop. This is also the number of CRLF's found. This sample does what you described. I counts the number of CRLF's found and it stops when the line is blank. There are some file formats that use only CR or only LF. If that were the case then you would have to read the entire file into a variable and parse through it. But, since Notepad+ indicates the file is ANSI format we know that each line of your file ends with CRLF.

The Text File Begin Process will read one line at a time and put it into your variable %T1% ... without a CRLF. Variable %T1% will not contain a CRLF. In your example the first time through the Text File Begin Process loop %T1% will contain "My Requisition Statuses" (no CRLF). The second time through the loop %T1% will contain "Create Requisition" (again, no CRLF). The third time through the loop %T1% will contain "Procurement Templates" (still no CRLF). To see how these things work load the file asniSavedCopy.txt into variable %T2%. Then do the "Variable Set Integer %N1% from Position of Text in variable %T2%. The variable %N1% will be set to 24 (Assuming the first line contains "My Requisition Statuses<CR><LF>" What are you trying to accomplish? We might be able to help you better if we understand your goal.

This worked for me: The /c parameter tells cmd.exe to close after running. %TEMP% points to the temporary folder. You could also put commands in a batch file c: cd %TEMP% dir > %TEMP%\DirCmd.txt and use the Program Launch command to run the batch file. And then, as rberg said, load the file into a macro via a 'Variable Set String %T1% from File' command or the Text File Begin process command.

Those log entries indicate that you have logging enabled for the "Open IrfanView & paste" macro. Edit the macro in the Script Editor. Click on the Miscellaneous tab. Click to disable "Log all Errors" and "Log all Commands". Normally I only use "Log all Commands" when I am debugging a macro.

If you post the content of your Macro Logs it would help us understand what is happening. Click Tools, Macro Logs to see the folder where the logs are saved.

That message means that something has been added to the Macro Logs. Have you looked at the logs?

Huh. I had never noticed that before. I got curious so I did some testing. Captured macros have: Text Type (Simulate Keystrokes): <DOWN ARROW><LEFT ARROW><RIGHT ARROW><UP ARROW> The Text Type command enters: Text Type (Simulate Keystrokes): <ARROW DOWN><ARROW LEFT><ARROW RIGHT><ARROW UP> Both forms work. Interesting.

Macros are saved in a file with the extension .mex. Search for the file(s) with .mex extension in the old profile and copy it to the new profile. Then click File, Open File to load it into Macro Express.

I would suspect your anti-malware software. At one time Windows Defender delayed the start of macros. That was later fixed. Currently BitDefender causes many delays on my computers.

The Lock Player and Unlock Player commands are added when you load a macro created in Macro Express 3 into Macro Express Pro 4. There is a checkbox that asks if you want to add them. Lock Player is used to prevent another macro launching while the first macro is still running. This has been useful to me on rare occasions. When you select an item in a popup menu a few things occur: 1. The popup menu disappears 2. The active window changes 3. The typing (or whatever the macro does) begins. It sounds like step 3 is starting before Windows finishes with steps 1 and 2. The amount of time to accomplish steps 1 and 2 can vary depending on the speed of your computer and what is running. The same macros on a different computer may behave differently.