In that case. Perhaps it would be better to store dynamic info in a different ini file.
I any case, o-- Dennis McGrath mailto:[EMAIL PROTECTED] -- Tools for R:BASE programmers http://www.enteract.com/~mcgrath/dennis -- Full time consultant with SQL Resources mailto:[EMAIL PROTECTED] should be able to lock down the RBASE.INI and RBASE.CFG files so they cannot be changed by a casual user. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Lawrence Lustig Sent: Monday, November 19, 2001 9:09 AM To: [EMAIL PROTECTED] Subject: Re: Placement of RBASE.CFG and RBASe.INI files > R:Base would do well to store dynamic data like recent files in the > registry, rather than in the INI file. That is where most programs store > this kind of information. The less you write to important files like this, > the less chance there is of them being corrupted. I vote a big NO on this idea. Using the registry for storage means that in the event of corruption, the entire OS is open for damage, not just the setup for an individual program. Also, the registry is much harder to edit for people who need to do manual configuration or who need to recover from some kind of problem. I used the registry for storing settings in the original version of R:Code, and have moved away from it in later programs. Sometimes the new ways are not better ways. -- Larry __________________________________________________ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com
