R
Raphael Boos
We have problems with filtering and sorting in an adp application dealing
with supplier data integration of multiple suppliers. We migrated from an
access2000 mdb to a sqlserver2000 based environment with an Access 2003
client. The application has been working perfectly for years. Only one single
user is connected to the database.
Forms are populated by different stored procedures. Most of them are very
simple, like --Select from table where condition1 or condition2--
Queries often return between 20000 and 50000 records. Number of records is
no performance probleme until you start to filter or sort by form. There is
no way to reduce the number of records returned - the idea of the interface
is that a user may edit a lot of product records very fast through
intelligent filtering and sorting.
Filtering or sorting only by one criteria via the form (filter by form)
makes the interface (a subform not linked to the master form) incredibly
slow.
The performance problem does not occur through the filtering/sorting itself,
it occurs after having done the work.
The form is repainted several times (no resizing), you can watch drawing
each single control. If you move the record pointer to the next record, the
same slow form painting occurs.
The subforms data is loaded by setting the recordsource property
programmatically to the name of the stored procedure. We tested connection
and recordset properties, default cursors are used (static client).
Thanks for any ideas.
Regards, Raphael
with supplier data integration of multiple suppliers. We migrated from an
access2000 mdb to a sqlserver2000 based environment with an Access 2003
client. The application has been working perfectly for years. Only one single
user is connected to the database.
Forms are populated by different stored procedures. Most of them are very
simple, like --Select from table where condition1 or condition2--
Queries often return between 20000 and 50000 records. Number of records is
no performance probleme until you start to filter or sort by form. There is
no way to reduce the number of records returned - the idea of the interface
is that a user may edit a lot of product records very fast through
intelligent filtering and sorting.
Filtering or sorting only by one criteria via the form (filter by form)
makes the interface (a subform not linked to the master form) incredibly
slow.
The performance problem does not occur through the filtering/sorting itself,
it occurs after having done the work.
The form is repainted several times (no resizing), you can watch drawing
each single control. If you move the record pointer to the next record, the
same slow form painting occurs.
The subforms data is loaded by setting the recordsource property
programmatically to the name of the stored procedure. We tested connection
and recordset properties, default cursors are used (static client).
Thanks for any ideas.
Regards, Raphael