Well, the issue is not really ms-access, but what data engine you use with
ms-access.
The default engine is a file share, and is called JET. if you use c++, VB,
or ms-access and JET, you will as general rule find NO DIFFERENCE in
performance.
You can also use ms-access with sql server, and once again, most of your
limits will be what ever the server limits are. So, once again, grabbing
records from sql server via c++, VB, or ms-access to sql server is NOT going
to make any difference (after all, sql server don't know that ms-access, or
a c++ program is grabbing records..and can't change the speed for some
reason!).
So, ms-access can work will with the JET engine, or sql server.
75,000 records is quite small, and should be really nothing for JET to
handle here. Since your files are so small in terms of numbers of records,
then the real question becomes what data engine you choose and for what
reason. For example, how many users do you plan to have, and how are they
going to connect to the data engine can make a big difference. (you can't
use the JET engine as a file share across a VPN for example..where as you
most certainly can do this with sql server).
So, I kind wanted to difference between ms-access, and the data engine you
choose, since with ms-access you have a choice of what engine to use (they
are somewhat separate issues). You should also note that for the last 3
versions of ms-access, there has been included on the office cd a desktop
edition of sql server for use with ms-access. So, you have a free version of
sql server included with ms-access anyway. However, unless you expect real
large file growth, or many users, or users that must connect to this data
over the net, then you likely don't quite need sql server just yet....
