DataSets can work natively with flat files or xmlFiles, so you don't have to write (and Test!) a lot of code! However, loading and saving 100MB could take a lot of time. You cannot afford to save the data before exit (well - still, you may use a special thread...) and if the system fails, you loose everything. Note that this is part of the new Microsoft standard for Smart Clients, wherever the background of the DataSet is a flat file or a database.
Horia -------------------------------------------------------------------------------- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Lisa Westveld Sent: Saturday, February 18, 2006 4:46 PM To: [email protected] Subject: [delphi-en] Re: Limitations of Access? --- In [email protected], Thomas Hruska <[EMAIL PROTECTED]> wrote: > > Your suggestion to load the entire database into memory is not a good > one. According to the OP, it is roughly 100MB...when you take into > consideration data structures and data alignment, loading the whole > thing would probably consume at least 300MB RAM. Well, if you plan to load it into memory then why use a database in the first place anyways? Why not put everything in one big flat file. Then add a few other files containing indices that you can use to search in your flat file. Might require you to write a lot of code and you'll be missing the dataset components but it could be a very fast solution for huge amounts of data. Isn't that the drawback of databases anyway? You gain a lot of speed in development but it costs a bit in performance. Greetings, Lisa. ----------------------------------------------------- Home page: http://groups.yahoo.com/group/delphi-en/ To unsubscribe: [EMAIL PROTECTED] Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/delphi-en/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
