>>>>>>By the way, you can, of course, have users have their own locations in the registry, possibly based on their Login ID, i.e. first time they log on a "strange" computer they have to define their prefferences, next time ther're already there.
>>>>>
>>>>>That's true. But if I just keep the INIs on the server, then it doesn't matter what computer they're on. And I don't have to futz with the registry.
>>>>>
>>>>>-Michelle
>>>>
>>>>I guess it's a matter of judgement. But when using INI you have to have a section for each user in it, right? That would be a drawback, as the size of the file would be pretty big for some apps.
>>>
>>>A section for each user? That's a cool idea. I was going to have an INI for each user.
>>
>>Note
>>Be careful about accesing the file, if you decide to go for a single file. Only one at a time, remember...
>
>Good point. I guess I'll go back to a file apiece.
>

Not exactly what I was aiming at. Reading the INI file doesn't take that long that user might get frustrated waiting on it. I just suggested you put reading the file in a time limited loop, in case the file is used by someone else. That will solve the problem. Guard yourself from that, and you'll be fine.