MSAccess & Client Server Configuration

[Beaula]

I would like to design a system with client server architecture for catering to 200 users. I would like to use MSAcess as the back end database with VC++/VB as front end. Can MSAcess support this kind of architecure & what will be the performance and security restrictions. Can any body throw more light on this ?.

 

[maxmangion]

having 200 users, access is definitely not the way to go.

 

[Beaula]

having 200 users, access is definitely not the way to go.

Can we develop a Client Server application with Microsoft Access 2000 Projects for 200 users ?.

 

[Kevin_S]

DO NOT USE ACCESS FOR THIS!!!!

your going to have to use a larger RDBMS like SQL Server, Oracle, DB2, etc...

HTH,
Kev

 

[Kevin_S]

Can we develop a Client Server application with Microsoft Access 2000 Projects for 200 users ?.

You could use an adp for the FE in and connect to a large RDBMS but I still wouldn't use access for 200 user ADP - use a VB/VB.NET/C/C++/C# FE for this... Some may differ on my suggestion here but unless you are extremely versed in Access (i.e. know its shortcomings and how to set it up to overcome them) I wouldn't try and tackle this with access...

HTH,
Kev

 

[maxmangion]

Kevin_S suggestion are the way to go to suit your needs. Having more than 10 to 15 users on an access db it will start being a pain in the ....

 

[The_Doc_Man]

Concur with max and kevin.

Access + 200 users = imperceptible movement. Snails would zip by you. Watching grass grow would be truly exciting. You probably could not stand the strain of watching something so fast as a sloth eating.

Use ORACLE, SQL Server, heck - even MySQL would be better than Access in this case. (But MySQL is kinda undersized for this, too, when you get down to it.)

Oh, by the way...

Access is NEVER the server side of client/server. You can build ADP stuff that will look at an Access database, but you won't be using Access itself when you do. You need a special license for IIS (if I recall correctly) in order to do this.

Access as a FRONT END can be the CLIENT side of a client/server situation with ORACLE or SQL Server as the back end. Works pretty well. Can be costly, though, 'cause you need a separate copy of Access for each user. Add it up. 200 users * Bill Gates's price structure = big budget nightmare.

 

[Kevin_S]

Access + 200 users = imperceptible movement. Snails would zip by you. Watching grass grow would be truly exciting. You probably could not stand the strain of watching something so fast as a sloth eating.

Now that is funny!

Thanks for making me chuckle at the end of a long day Doc... good points too!

Kev