Reducing size of forms recordset

  • Thread starter Thread starter mbosman
  • Start date Start date
M

mbosman

I have a front end and back end situation; both are
mdb's. I am going to be giving a location in Canada a
front end copy to enter data. Since they will be
accessing the back end over a network I'm curious if it
is possible to reduce the size of the forms recordset to
decrease the network footprint and improve performance
for them. Can this be accomplished by a where condition
in the docmd.openform statement. I've been told it is not
possible, but there's got to be a way around it. Possibly
setting the form's recordsource to an empty string at
close and resetting to a SQL statement that effectively
shows only the correct records at load? Any body have any
good ideas?
 
mbosman said:
I have a front end and back end situation; both are
mdb's. I am going to be giving a location in Canada a
front end copy to enter data. Since they will be
accessing the back end over a network I'm curious if it
is possible to reduce the size of the forms recordset to
decrease the network footprint and improve performance
for them. Can this be accomplished by a where condition
in the docmd.openform statement. I've been told it is not
possible, but there's got to be a way around it. Possibly
setting the form's recordsource to an empty string at
close and resetting to a SQL statement that effectively
shows only the correct records at load? Any body have any
good ideas?
Click to expand...


Not sure you can't do this using OpenForm's WhereCondition
argument. If not, then leave the form's RecordSource
property unspecified and construct its SQL statement in its
Open event.

Regardless of how you end up doing it, make sure that the
fields used in the Where clause are indexed. Access will
bring the indexes across the WAN and use those in an attempt
to minimize the number of data blocks retrieved.
 
Without question, using the where clause will reduce the number of records
transferred to a mim (assuming the key value used has a index).

However, the problem is that the internet is very VERY slow as compared to a
office lan.

You can read the differences in speed and some solutions here:

http://www.attcanada.net/~kallal.msn/Wan/Wans.html

The best solution is to use remote desktop (or terminal services, which is
the same as remote desktop).
 
Back
Top