I've found that if you're accessing that info from multiple environments (VFP, C, VB), then it works pretty good (although I suppose you could do this with a .ini too) MS started recommending registry over .ini at some point I think because they optimized the registry for speed. You can also create a simple VFP frontend for your users to easily update and change the registry.
You might want to also consider just a .dbf if you're only accessing the info from VFP since it's already highly optimized...
>I'm wondering, what are the benfits of using the Registry (in wni95+ OSes) versus keeping our old INI files.
>
>I guess most importantly, do these benefits really warrent going back through all our code and convertnig from INI file dependency for initialization stuff to Registry dependence?
>
>Thanks
>Matt