As a few others have mentioned, you likely can find the setting to allow
more then 10,000 records.
However, allowing that many records to funnel into a form is likely not the
best idea here. If just two users open up a form..you can potentially
shuffle 20,000 records across your network..and you not done one bit of
useful work yet!
All of a sudden, your network admin will ask why is this application
swamping the network?
And, if anyone with good IT experience sees this system running will ask why
such large records numbers being transfer with no useful work being done?
And, then the next thing you know they are telling you that ms-access is no
good, and the whole thing needs to be re-written in .net. Ms-access
performances just as good as C++, or any other programming language when you
use it to connect to sql server. However, you do want to limit the amount of
data transfer by your designs. Those other systems are not better..but they
don't encourage with such ease the ability to just open a form to a large
table.
If you think about this, a install teller machine does not first download
all the accounts, and THEN ask you what account (pin) number to work on. In
fact, the reverse happens.
So, you should ask the user what customer, or account number, or invoice
number etc (or whatever), and then load up the form with the ONE record (and
possible related detail records). The user can then deal with the one
customer, or do the one task, and then exit back to the search/prompt screen
ready to do battle with the next customer. Try running any other application
you have that deals with lots of records..and note how it works...and again
you will see that large tables are not just thrown up to the user.
Anyway, I just trying to give you a few pointers, and if you figure out what
the user need to work on, prompt that user, then the result is the
application now has only loaded one record in place of 10,000. That is
10,000 times better, and your network (and server) will not get swamped. SQL
server is a very fast and powerful system, but you have "ask" the server
what you want to work on...and if you just transfer large amounts of
stuff..it tends to run slower then just ms-access without sql server!
So, I am going to leave it up to other posters to point out the option
(wherever it is) to increase the number of records being pulled into the
form..but really, that is asking for more rope then you really need!
Here is some ideas of what a nice screen prompt concept that works very well
with sql server.
http://www.attcanada.net/~kallal.msn/Search/index.html
Good luck!
