I presume we're not the only ones who use some custom settings to prevent hard-coded paths, usernames, timeouts etc.
At the moment we keep a set of public constants in a central script.
This approach works, but user access to the settings is limited and I'd like to have a user-editable text file, in xml or ini format - this also has a benefit of adding at least one dimension to the settings to make them more robust (at the moment we use prefixes, e.g. FN_ for file names)
Bottom line I want to be able to access the data from VBScript using something like MyPath = CustomSettings.MyPathValue
Ah, I see. It wasn't clear that you were thinking of users who couldn't use TC for editing. That is a common problem.
You could use a script file that simply isn't included in your version control system. That gives you the best of both worlds; editable both in and out of TC.
Personally, I have used both xml files and spreadsheets for this sort of thing in the past, but I am currently moving towards a database system. More work to set up, but so far it has been totally worth the effort.