Christophe,
That's part of the point of the IniArray UDF suite. It uses standard File I/O to load the entire INI file into an array once rather than using multiple Read/WriteProfileString functions. The other purpose of this UDF is that it removes the 32/64K size limit of INI files. My earlier reference of a 600ms performance improvement was moving from ReadProfileString on a locally cached file to loading the same local file into IniArray and using ReadIniArray calls instead.
On a WAN, local caching of a 12K file before loading into IniArray will save between 0.4 and 1.3 seconds, depending on WAN speed. Directly reading the INI on the server with ReadProfileString is much worse and local caching has been known to knock off 15-20 seconds! This is why our Universal Login Script has been caching the INI file on local disk since 2006. The IniArray UDFs just take it to the next level, managing all INI functions in RAM.
Glenn
_________________________
Actually I
am a Rocket Scientist!
