Leaderboard

Good point Jos. I totally forgot about that. Have a look at Running under Windows 64-bit Edition in the Help File. Try adding the following to the the top of your script. #include <WinAPIFiles.au3> ;Disable x86 redirection mechanism for a 32-bit script. If @OSArch = "X64" And Not @AutoItX64 Then _WinAPI_Wow64EnableWow64FsRedirection(False) Adam

First, check the folders in the ISN settings. Go to File -> Settings -> Program Paths. Here you will find "path for finisehd projects". This is the default folder ISN will move compileds projects to. And you can also adjust this behavior as follows: Check Project -> Project settings -> Compile settings. Here you can choose 2 modes. First is to move the compiled porject in the "finished projects" folder (default) or second to simply create an subfolder in the project which contains the compiled stuff. And for much more personalisation you could also make a makro to a macroslot. So..what the hell are macrosolots? These are simply 1-7 Slots you can assin custom actions to. They will be displayed in the toolbar and the "tools" menu. You can create these under Project -> Marcros. For example you could create a macro that compiles you file 1, 2, 3.. to custom directories and so on. Assin this to a macroslot an you can simply "trigger " the macro by a click. Hell you could also assign a hotkey in the settings to an macroslot I think, some of that will help you

Have you tried it with DirRemove?

The whole point of pausing the script is so that it stop processing until you unpause it. That would defeat the entire purpose of pausing the script. You can't do something if you tell it to stop doing anything.

Fails because _GUICtrlIpAddress_Create retrieves a handle. Func Btn_Zaloguj() $read1=GuiCtrlread($IpAddress) _IENavigate($oIE,_GUICtrlIpAddress_Get ( $IpAddress )) EndFunc

as long as you keep the json request a one liner i had no problems.

Yes, it can be done in many ways. Instead of google sheets and so on , you can just get the balance via the IE functions and then write it in the excel file with the excel functions.

Hi! I am the developer of the ISN AutoIt Studio..and i will expanin this behavior for you: At first it makes a difference if you have the advanced debugging enabled. If it´s enabled, the isn "injects" some code to you script (to make it debuggable) when you run it. And this code has it own includes with already includes stuff like $SS_SIMPLE and so on. So if you have advanced debugging enabled it will crash at your declarations because they are already declared through the injected code. And when you compile the script (or run it wit advanced debugging disabled)..the debug code is (of corse) not included...and so the constants are missing in this way -> Crash. Solution? The solution to this is pretty simple: Just use the official includes (where the constants are defined) and do not redifine it at your own. AutoIt Includes are marked as #include-once..so they can in theory stand 100 times in your script, it will only include the stuff in it once. And in your case simply remove the constants from your script and update your includes to this and it should work. (In the ISN with or without advanced debugging and compiled) #Region ;************ Includes ************ #include <EditConstants.au3> ;for $ES_AUTOHSCROLL and $ES_READONLY #include <GUIConstantsEx.au3> ;for $GUI_EVENT_CLOSE #include <StaticConstants.au3> ;for $SS_SIMPLE and $SS_SUNKEN #include <SQLite.au3> #EndRegion ;************ Includes ************ Feel free to send me a message about ISN questions

This should help FernanS1. After reading Water's great comment, I tried for the 1st time to use a COM error function (i'm totally newbie with COM) while simplifying FernanS1's script during debug time, This is the simplified script : #include <Excel.au3> #include <MsgBoxConstants.au3> LoadDictionary() Func LoadDictionary() Local $oErrorHandler = ObjEvent("AutoIt.Error", "_ErrFunc") Local $oExcel = _Excel_Open() Local $oWorkbook = _Excel_BookOpen($oExcel, @ScriptDir & "\CUDictionary.xls") Global $oDictionary = ObjCreate("Scripting.Dictionary") Local $vw = $oExcel.Activesheet.Range("V1:W10").Value For $i = 0 to 9 $oDictionary.Add($vw[0][$i], $vw[1][$i]) Next Local $yz = $oExcel.Activesheet.Range("Y1:Z16").Value For $i = 0 to 15 $oDictionary.Add($yz[0][$i], $yz[1][$i]) ; THIS IS LINE 19 Next $oExcel.quit EndFunc Func _ErrFunc($oError) MsgBox($MB_SYSTEMMODAL, "COM Error intercepted !", _ "script name :" & @TAB & @ScriptName & @CRLF & _ "err.scriptline : " & @TAB & $oError.scriptline & @CRLF & _ "err.number : " & @TAB & "0x" & Hex($oError.number) & @CRLF & _ "err.windescription :" & @TAB & StringStripWS($oError.windescription, 1+2) & @CRLF & _ "err.description : " & @TAB & $oError.description & @CRLF & _ "err.source : " & @TAB & @TAB & $oError.source & @CRLF & _ "err.helpfile : " & @TAB & $oError.helpfile & @CRLF & _ "err.helpcontext : " & @TAB & $oError.helpcontext & @CRLF & _ "err.lastdllerror : " & @TAB & $oError.lastdllerror & @CRLF & _ "err.retcode is: " & @TAB & "0x" & Hex($oError.retcode) & @CRLF) EndFunc ; ==> _ErrFunc When this script is run, even without any @error test in the script (which is strange), the _ErrFunc will be activated and its MsgBox() will appear exactly 10 times with the same content, so we'll have to press Ok 10 times, here is the COM error : A google check on the error return code shows this : VBScript Error Codes : (0x800A01C9) "This key already associated with an element of this collection" I indicated in the script which line is line 19 (the error line), it corresponds to the update of the dictionary with data taken from columns Y&Z So it seems that the values found 10 times in column V were correctly added to the dictionary, but when the script tries to add columns Y&Z, it cannot add them because 10 cells from column Y are exactly the same as 10 cells from column V If you want to run the script, you'll have to download FernanS1's excel file (attached in his 1st message) Good luck FernanS1 for the future and thanks Water for the good advice, I won't forget it

Add a COM error handler to your script for more detailed error description. See ObjEvent in the help file.

For people new to SQLite, I'd recommend following the step by step approach: o) First install a nice 3rd-party SQLite DB manager named SQLite Expert o) Used this to design your DB o) Use the SQL tab to run the various SQL queries and statements you expect to be using o) Fine-tune the design as necessary o) Only then start coding your fancy GUI app.

$s_AttachFiles = "attachment1.au3;attachment2.au3;attachment3.au3;attachment4.au3"