Originally Posted by Minty
To be honest it's not considered good design to open a form and load all the underlying records.
The normal route would be to load the form "empty" and to give the user some search features and then only retrieve those records that meet their needs.
As you get into bigger datasets this will become essential to stop things bogging down.
You are right.. this is the technique I use when I develop web applications due to browser considerations. But a desktop application is more flexible on this issue.
In this case, records are few to worry about, and the growth rate is only about 2500 new records per year!
Also the concurrent users are about 10... Not so many to create a problem with sql server!