Ok, here's how I got it to work with the array and it'd indicies:
Code:
For Each $proc In $PList
$proc1 = Split($proc,"*")[0]
$proc2 = Split($proc,"*")[1]
$proc3 = Split($proc,"*")[2]
$processSQL = "INSERT INTO processes(cid,Name,ProcessID,ProcessPath) VALUES('$cid','$proc1','$proc2','$proc3')"
$ = DBExecuteSQL($objConn,$processSQL)
? "Error @ERROR: @SERROR"
Next
Bryce: Thank you for the suggestions but they were a little off. Values is not a UDF, it's a MySQL/SQL command. It's apart of the $processSQL line. I was just asked on my last post to break up my SQL statements with a return character so that the code didn't break this forums tables out to more than 2500 pixels again. And my quotes aren't all over the road, if KiX supported array elements in strings, this is probably exactly how it would look. There are just a lot of quotes because I'm stepping out of the text portion of the variable and using a fuction and concatenating them together inside the string.
Bryce/Les: What is so evil about using variables in strings? It's great and it makes coding so much easier. Is there a security aspect I'm missing or is it just your coding preference?
