I would tend to agree. Use some form of relational or file based database
store.
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"Dan" wrote:
| Hi all -
|
| I do custom programming and network support. A client recently handed off
a
| program to me that they'd had written by someone else. It runs on a
Windows
| 2000 Server.
|
| From what I can tell the original author is using the registry as a simple
| database - reading in values on initialization (normal enough), then doing
| large amounts of reads and writes / creation and deletion of string values
and
| longs as the program runs. When exported the registry key for this program
is
| about 10 megs - All of the program's data storage is in the registry.
|
| While I've used the registry in the past for program initialization,
saving
| the state of an application, etc.I have never seen the registry used like
this
| before. Am I out of the loop? Is this something common?
|
| I'm considering rewriting the data storage portion of the program - this
just
| doesn't smell right to me.
|
| Thoughts? Opinions? Thanks in advance.
|
| - Dan
|