Leaderboard

@Schnuffellets continue this discussion in PM to keep it clean and consise so we are able to tackle 1 part of you steps at a time starting with your x64 option for a3x so you fully understand how things work. Please PM me with an simple answer whether you have understood what I've explained on that topic!

Am neither of them but the answer to a tiny install is: no. The a3x file is the tokenized file that is included as a resource for the stub ( the executable ). It can be given any extension name. So it can run from within the stub ( as compiled executable ) or referenced as external resource ( as file ) ...the black hat issue is that I brought up given that you rather not inform the user of the interpreter of the file/ In that regard, I invented pain. Or so I thought until I learned that is common place. Then again am lucky that I didn't come up with something that produced death Again, am not against your wish of a better distribution for our work. If someone ( maybe you ) comes up with something OMG!, @UEZ will take a lower standing in my list of gods ( I call god those that can do what I never could yet ) and you'll be my favorite god

As I see it, you have to group and filter data, create totals for the groups, etc. This literally cries out for a job for SQLite. Once you have the data in an SQLite database, the groupings and totals are a piece of cake. To do this, however, you would first have to define a basic structure for this table in the database. In other words, which columns have which names and which data type. The import is then best done in milliseconds via _SQLite_SQLiteExe() in conjunction with the .import command and tabulator as column separator. Otherwise, it is not yet clear to me personally how you get from the input data to the table that you designate as desired output. The model is hidden somewhere as a substring in the 4th column. The rules for extracting it are not clear. And I also don't understand how these values of 140 are created from the initial values. No sum, average or anything else that you could derive from your example extract results in your desired values. Of course, you can also handle the import, filtering and grouping with pure AutoIt. But then I would recommend that you use ready-made UDFs to help you. Here is an example of how you could proceed with your data using the TableData UDF, for example: #include "TableData.au3" ; Transfer data to table type - customize attribute names in the header to your needs $mData = _td_fromCsv("Big_Data.txt", @TAB, 0, "Attrib1|Attrib2|Attrib3|Model|Attrib5|Attrib6|Process|Attrib8|Attrib9|Attrib10|Attrib11|Attrib12") ; display data _td_display($mData, "Big_Data - whole dataset") ; group by model and process - the example here attempts to extract the model from the model column and concat it with the process to form a group string $mGroups = _td_groupBy($mData, "__extractModel($x.Model) & ' | ' & $x.Process") ; Go through the individual groups and process them. Here you could do your sums or whatever For $sKey In MapKeys($mGroups) ; the current group data as table object $aGroupData = $mGroups[$sKey] ; calculate the sum over the 8th attribute for the current group $fSum = _td_reduce($aGroupData, "+ $x.Attrib8", 0) ConsoleWrite(StringFormat("% 70s: %6d\n", $sKey, $fSum)) ; display the current group data ;~ _td_display($aGroupData, $sKey) Next ; auxiliary function to extract the model name from the total string in the 4th column. You will certainly have to adapt this to your needs Func __extractModel($sString) Local $aSplit = StringSplit($sString, ",", 3) If UBound($aSplit) < 2 Then Return $sString Return $aSplit[1] EndFunc