Access Capabilities

  • Thread starter Thread starter AJOLSON
  • Start date Start date
A

AJOLSON

I was wondering what is the # of files that access can run effectively in?
I have a client that has about 150,000 records with 25 users within the same
LAN. I know that is a very broad question but just want to make sure Access
is the proper DB to handle this.
 
I was wondering what is the # of files that access can run effectively in?
I have a client that has about 150,000 records with 25 users within the same
LAN. I know that is a very broad question but just want to make sure Access
is the proper DB to handle this.
Click to expand...

I'm aware of at least one working Access database with 20,000,000 records in
the largest table. In addition Access can use SQL/Server or Oracle or any
other ODBC database as the data storage medium, making it effectively
unlimited.
 
AJOLSON said:
I was wondering what is the # of files that access can run effectively in?
I have a client that has about 150,000 records
Click to expand...

A table with 150,000 records is extremely small, and you can generally
process that kind of data in well under a second.
with 25 users within the same
LAN.
Click to expand...

The real question becomes what are you using for your back end for the
database part?

25 users on your network is not a problem. Without question your
application is likely split into a front end part or so called application
part that gets installed on each WorkStation. Each of these applications
installed on each PC will then connect your server where the data resides .

You can use what is called a file a share in which all front ends open/share
the back end database file. However, since there are so many free data base
servers, then you can have the access application connect to this database
server (be it oracle, sql server etc.

So, you really don't have a limit of users from the ms-access side as much
as what the server side is....

Don't confuse MS access as a tool which allows you to develop applications
compared to that of a database engine that serves data to the access
application. These are completely separate concepts.

So, 25 users was only going to be an issue if you choose the wrong database
engine in which to work with for your access application.

So, 25 users in ms-access is not a problem at all, the issue becomes what
data engine you are going to use with ms-access.....
 
Back
Top