B
Baby Face Lee
Hi all,
I've produced an Access 2002 d/base for users to input/amend certain data.
I've got the FE installed on user's PCs and the BE on a server. There are up
to 6 or 7 users at one time and they're often complaining that it's slow and
frustrating to use.
I've tried to improve things where I can (like using the trick that keeps a
tiny recordset open in the background) and avoiding DLookups (I've got one
ELookup which is supposed to be twice as fast).
I'm now going to pass the amending of data into a different form (where
there is already a record for the client) so that I can 'push' the data into
the table from a Data Entry form for any new (additional) records and thereby
make the form unbound to a recordsource. The data entry form comprises a
main form with a (continuous) subform. What I'm not sure of is whether I
should push the data after each record on the subform is completed or wait
until the user's finished entering all the data for the client and then push
it. Either way I'm not too sure how!!! I presume that as I would need to
open the recordset (if I did it this way rather than use SQL) each time a
record is saved, it would be better to save all records for a client at once
(?) Would using SQL be better from a performance point of view?
Any advice would be very welcome!!!
Thanks folks!
Lee
I've produced an Access 2002 d/base for users to input/amend certain data.
I've got the FE installed on user's PCs and the BE on a server. There are up
to 6 or 7 users at one time and they're often complaining that it's slow and
frustrating to use.
I've tried to improve things where I can (like using the trick that keeps a
tiny recordset open in the background) and avoiding DLookups (I've got one
ELookup which is supposed to be twice as fast).
I'm now going to pass the amending of data into a different form (where
there is already a record for the client) so that I can 'push' the data into
the table from a Data Entry form for any new (additional) records and thereby
make the form unbound to a recordsource. The data entry form comprises a
main form with a (continuous) subform. What I'm not sure of is whether I
should push the data after each record on the subform is completed or wait
until the user's finished entering all the data for the client and then push
it. Either way I'm not too sure how!!! I presume that as I would need to
open the recordset (if I did it this way rather than use SQL) each time a
record is saved, it would be better to save all records for a client at once
(?) Would using SQL be better from a performance point of view?
Any advice would be very welcome!!!
Thanks folks!
Lee