[quote:pf1ut1zd]When I open big tables several times during app execution doesn't this lead to
out of memory or very slow opening of that table?
Adordd builds each table recordset only once.
If your table recordsets have million of records you will need enough memory for it and it can easily
reach some hundred MB or more.
When you open that table again the memory consumption its minimum as adordd clones that table set, which
means a kind of pointer to previous open recordset being extremely fast opening it again and very
low on memory use.
[/quote:pf1ut1zd]
I am not clear on this. If every user has their own copy of all the databases in memory, then how do those databases get updated in real time when other users change them? If this doesn't happen, then how can this design be useful?
James
↧