Avatar of Anton Greffrath
Anton Greffrath
Flag for South Africa 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?
Microsoft Access

Avatar of undefined
Last Comment
Anton Greffrath

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Paul Cook-Giles

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
PatHartman

If your BE is a RDBMS, it is far better to severely limit the number of rows returned as the recordset of a form.  You loose any speed advantage you might gain from SQL Server if you bring unfiltered recordsets across the network in order to filter it locally and the larger the recordset, the larger the cost of doing it.

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.
Anton Greffrath

ASKER
Thanks Paul Cook-Giles, I implemented your solution and it worked 100%
Anton Greffrath

ASKER
Export Exchange Rocks!
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
Anton Greffrath

ASKER
Thanks Paul. . . .