Do you mind if I open Robert's question up just a little, to make the responses even more edifying to a newbie? ... How does one go about planning the kind of data structure to use for storing information, given the number of choices--home made scheme with text file, name-value pairs and string lists, ini file "database," records, XML, etc. I'm thinking about situations where a separate database is not involved. I recognize speed issues are important as the amount of data to be stored/retrieved increases. I'm new enough to programming that I'm still thinking more about how long it takes *me* to write the code than for others to use it :)
I'm trying to keep this as a general question; I'm learning a lot -- still, I'll add I often have a 'field' that includes a large amount of text. I'm under the impression that records either can't handle this, or would be a poor choice because of having to set aside a large chunk of memory in each record, even if the stored text was sometimes small. Is this accurate? Thanks for the lessons! Al C. _________________________________________________________________ On the road to retirement? Check out MSN Life Events for advice on how to get there! http://lifeevents.msn.com/category.aspx?cid=Retirement _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
