Re: Network Efficiency
- From: "David W. Fenton" <XXXusenet@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 19 Jul 2006 19:06:25 -0500
perryche@xxxxxxxxx wrote in
news:1153273248.329538.143490@xxxxxxxxxxxxxxxxxxxxxxxxxxx:
I know having a better network (faster), increasing RAM, goto SQL
server... are not options for me at my work. It will take much
more than what I am able to change there. Therefore, the only
options I have are: split the DB to FE and BE, Break up Table to
smaller ones, Use VB codes that have an error handler, what else?
The main thing is to request and load only the smallest data set
that can satisfy a user's needs. That means for regular forms, one
record at a time, for continuous forms as subforms, only the records
belonging to the parent record, for combo- and listboxes, fewer than
100 records, with rowsource assigned only after a couple of
keystrokes are typed when you have more than 100 or so records in
the table it's based on.
That's just for starters. The main thing is:
Never bind anything with a recordsource/rowsource to a full table --
always filter to the smallest dataset possible.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.
- Follow-Ups:
- Re: Network Efficiency
- From: perryche
- Re: Network Efficiency
- References:
- Network Efficiency
- From: perryche
- Network Efficiency
- Prev by Date: Re: SQL and Parentheses
- Next by Date: Re: Align scrollbar in Access 97
- Previous by thread: Re: Network Efficiency
- Next by thread: Re: Network Efficiency
- Index(es):
Relevant Pages
|