water

I see. Then I suggest: Global $iRow ; Loop starts here $iRow = _ArrayAdd($Chart,$name) $Chart[$iRow][1] = number($change_1h,3)

This code returns a String as AutoIt internally converts your number to a String again to be able to concatenate them. $name & "|" & number($change_1h,3) Call _ArrayAdd twice to fill the two columns. See the help file for details: "String datatype elements are sorted alphabetically and number datatype elements are sorted numerically - it is important to ensure that elements are of the correct datatype before sorting."

I use the following function (taken from the forum): ; #INTERNAL_USE_ONLY# =========================================================================================================== ; Name ..........: _Ansi2Oem ; Description ...: Translates a string from ANSI to OEM. ; Syntax ........: _Ansi2Oem($sText) ; Parameters ....: $sText - Text to translate ; Return values .: Success - Returns the translated text ; Failure - None ; Author ........: Zedna ; Modified ......: ; Remarks .......: ; Related .......: Oem2Ansi (see link below) ; Link ..........: https://www.autoitscript.com/forum/topic/201398-german-umlauts-and-console-programs/?do=findComment&comment=1445253 ; Example .......: ; =============================================================================================================================== Func _Ansi2Oem($sText) Local $aText $aText = DllCall('user32.dll', 'Int', 'CharToOem', 'str', $sText, 'str', '') Return ConsoleWrite($aText[2]) EndFunc ;==>_Ansi2Oem

Why not write the state of all Radios to the Ini-File? Then read the needed key or all keys of the section and set the Control to the needed state. No need to store the name of the variables nor the control-Ids as this is information already available in the script.

IniRead returns a String, but GUICtrlSetState requires a ControlID which IIRC is an integer. So GUICtrlSetState(Int($Radio_click), ...) should work (untested).

Hi gcue, I will. My vacation starts on Friday

Or you create a script that runs daily/weekly/... at nighttime to extract imployeeID and SamAccountName of all users and store this information in a text file or database for faster access.

As you can see here property "proxyaddresses" is an indexed property and "employeeID" is not. Hence the difference in processing time. If needed you can add property "employeeID" to the list of indexed properties.

Added to the wiki

Parameter 2 of _DateTimeFormat isn't used in the correct way. Please have a look at the help file and you will understand what I'm talking about

You know that this thread is ~ 13 years old? The OP has left 2011, Excel has changed a lot and the Excel UDF had a full rewrite. So please open a new thread and provide more information so we can help you to fix your problem. At least post your source code, the version of AutoIt you run plus the error messages you get in the SciTE console when running your script.

The Excel and Word UDFs have been part ot the AutoIt package for ages (at least 2008). Some years later Jon/the Devs decided to not add more UDFs to keep the package small and easy to maintain. So new UDFs (like the PowerPoint UDF) have to be published in the forum. Big advantage: You can fix bugs or add new functions frequently and release a new version every day.

Never had to work with themes. But I think you should simply apply an existing theme as described here. Example: $oPresentation.ApplyTheme("C:\Program Files\Microsoft Office\Templates\MyTheme.thmx") Edit: Not fast enough

You need to add error checking to your script. Means: Add a COM error handler. See ObjEvent in the help file. Check @error and @extended after each line of code

Please do not edit the original post. For future readers the rest of the thread then does not make any sense