When I teach my scripting class, one of the guidelines is to consider your data elements, plan how they are organized, then write the code to load, manipulate, and then possibly write/update the results.
I do this with every script no matter how simple. For Kix, I create the INI file to hold and manage my data before the script writing begins. Next, I write the script header and fill out blocks of comments to describe each processing component. Finally, I flesh out the logic, block by block, testing as I go. Takes a bit longer to complete development, but I'm using Kix scripts to perform monitoring, maintenance, and alert processing for thousands of endpoints.
FYI - the IniArray is slightly slower than direct reads, which is why I don't use it in my login script (where performance must parallel reliability), but most other applications that have more than a section or two do use it. LARGE (over 64K) INI files do read slowly, but there's no other way to use them. Allen's got some pretty large INI files he manages with this UDF.
Glenn
_________________________
Actually I
am a Rocket Scientist!
