-----------------------------------------
This is based on my findings and is not intended to be the final word on case sensitivity within Macro Scheduler. Anyone is welcome to jump in with corrections when they find any of the statements to be in error or add where the findings are incomplete. The testing was done using Macro Scheduler beta version 9.045.
-----------------------------------------------------------------------------------------------------------------------
Case sensitive items:
- Labels
- Subroutine names
- Dialog names in the dialog definition
- The variable CENTER used to define the position of a dialog must be all upper case.
- Variable values:
For example:
Let>var1=test
Let>var2=TEST
var1 does not equal var2
because
test does not equal TEST
- Window names
From Help for WaitWindowClosed:
Windows can be successfully found and used by Macro Scheduler even if the name specified in the macro is not in the correct case. However, Help clearly specifies that using incorrect case for a window name may be detrimental in some instances.It is best to try to provide an exact (including case) window title to ensure the correct window is found, as many applications have multiple invisible windows with similar names. Specifying text without a trailing asterisk will force Macro Scheduler to only look for an exact match.
- The object_caption in GetCheckbox and SetCheckbox functions
- The values HIDE, NOSYSTRAY, LOGFILE and new to version 9 NOSTOPKEY
When compiling macros, running macros using the macro function or running macros from a command line, these arguments must be entered in upper case.
- RegistryDelKey
- RegistryDelVal
- RegistryReadKey
- RegistryWriteKey
In all of the Registry functions, the "root_key" argument value must be entered in all upper case. The other arguments seem to be case insensitive.
NetWork Functions:
The following Telnet, Ftp and HTTP items will have case sensitive arguments if the host they are connecting with responds to case sensitivity.
- TelnetConnect
- TelnetSend
- TelnetWaitFor
The "Host" and "Text" arguments will probably be case sensitive
- FTPDelFile
- FTPGetDirList
- FTPGetFile
- FTPPutFile
- FTPRenameFile
The "Server", "Username", "Password", "Host_File_Spec", "Local_File" and "New_File_Name" arguments will probably be case sensitive.
- HTTPRequest
"URL", "LocalFilename", "POST_Data", "ProxyServer", ProxyUsername" and "ProxyPassword" arguments will probably be case sensitive.
-----------------------------------------------------------------------------------------------------------------------
Case insensitive items:
- Macro Scheduler function names (Version 5 and greater)
- System variable names
Help singles out OS_VER, WIN_DIR, SYS_DIR and TEMP_DIR as variables that "store their values in upper case." However, testing these with version 9, all of them worked for me when typed in lower case.
- User defined variable names
- Dialog calls such as Show>DiaLogName or CloseDialog>dIAlOGnAME
- VBscript
- File paths and names
.
