shadow9449
Registered User.
- Local time
- Today, 11:03
- Joined
- Mar 5, 2004
- Messages
- 1,037
I've seen the suggestion a number of times that forms be designed to only load the one record from the table that the user wants to deal with at the moment. This is accomplished by binding the form to a query that returns the one record the user has selected (from a combo or list box, for example). The rationale behind this design as opposed to loading the entire table when the form loads is that it results in less data being loaded into memory and being drawn across the network, thus improving performance.
My question is that I've seen a number of times that Access needs to load an entire table into the client's PC i(and I would assume into RAM as well) in order to retrieve a single record. If this is true, then using one record for the datasource of a form won't have any improvement over using the entire table.
Can someone shed light on how Access actually loads the data into the record to explain why this design is more efficient?
Thank you
SHADOW
My question is that I've seen a number of times that Access needs to load an entire table into the client's PC i(and I would assume into RAM as well) in order to retrieve a single record. If this is true, then using one record for the datasource of a form won't have any improvement over using the entire table.
Can someone shed light on how Access actually loads the data into the record to explain why this design is more efficient?
Thank you
SHADOW