Thanks Robert, Which newsgroup?
If I understand correctly the scheme described, a standard table would have an essentially identical in-memory table that would act as a cache holding all the data that would be involved in any screen refreshes that would need to iterate across new and old data. It would seem some sort of mechanism would need to keep track of which data in the in-memory table has yet to be transacted to the standard table to keep from transacting the whole in-memory table with each transaction update. I've been reading up on using a TClientDataSet as a possible piece of the solution. > Message: 3 > Date: Fri, 4 Aug 2006 09:02:00 -0400 > From: "Robert Meek" <[EMAIL PROTECTED]> > Subject: RE: Database Design Suggestions > To: "'Moderated discussion list about database programming with > Borland's Delphi'" <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > We were just talking about a situation much like this on another > newsgroup. And it was pretty much decided the best way to go would > be to add the data as it comes in to an in-memory table, running any > queries and or filling any grids directly from it. Then at a set > interval or when idle use a transaction to Post the data. At the > same time any data no longer relevant to the user could be deleted > from the memory table. > > from Robert Meek dba Tangentals Design CCopyright 2006 > Proud to be a moderator of "The Delphi Lists" at elists.org _______________________________________________ Delphi-DB mailing list [email protected] http://www.elists.org/mailman/listinfo/delphi-db
