Anton Greffrath
asked on
Number of records returned on a form
I have recently converted my Client's MS Access database to an SQL Database. After the conversion I have the following issue:
I have a Form, based on a Query as the record source. When a subset of the records in the table (that the query is based on) is selected, the number of records returned in the subset is not displayed at the bottom of the form.
When MS Access the information was available. At the bottom of the form where it states: Records 1 of nn where nn is the number of records. after the conversion the nn is not there.
Any one that can assist to get the nn value showing again?
I have a Form, based on a Query as the record source. When a subset of the records in the table (that the query is based on) is selected, the number of records returned in the subset is not displayed at the bottom of the form.
When MS Access the information was available. At the bottom of the form where it states: Records 1 of nn where nn is the number of records. after the conversion the nn is not there.
Any one that can assist to get the nn value showing again?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Paul Cook-Giles, I implemented your solution and it worked 100%
ASKER
Export Exchange Rocks!
ASKER
Thanks Paul. . . .
Typically, Access only retrieves enough records to populate the visible rows of a form. It then requests additional rows in the background or as you scroll through the recordset. By having to see the n value from Record 1 of n, you are forcing Access to bring down all the records in the recordset whether the user ever will actually need to view them or not.
Many people who convert Access applications from Jet to SQL Server are flabbergasted when the app is sluggish and slower than it ever was with the Jet BE. Access is tuned to work with Jet/ACE. You have to take some control to get that same kind of performance against linked SQL Server tables. And the best place to start is to change your method of filtering. Let the user enter selection criteria to bring down as few rows as possible. Then change the selection criteria to go back to the server to get a different set of data.