MS Access for a multi user environment

[Sathyaish]

How is MS Access for a multi user environment? I guess its not up to the mark, but the client is bent upon having MS Access at his head office. I wish to know what are the issues in having MS Access as a database for multi user environments. Also, how do I make MS Access for a multiuser environment? And finally, if I am to use only MS Access and no other database in one application, which one'd be a better choice - DAO or ADO? Why?

[onbliss]

I would go with ADO. There is not much point in sticking with the older data access technology - DAO.

[Sathyaish]

Thanks for taking the time to read and answer my query.

[JFK]

How is access in a multiuser environment?

It would depend on how many users you intend having I have approx 20 - 25 users using ours on one site and it performs adequately.

I made our database have a front end and a back end. The front end with all the forms reports etc sit on all the user workstations then you make the ado connections connect to the server where the back end sits with all the tables.

JFK

[Ecniv]

I agree with JFK

Also ADO/DAO ... well its up to you.

If you know one of them, use that, they are pretty much the same with access and you can flip between them easily enough.

If you know nothing then learn ado as this will be more flexible if you want to move to VB later on. DAO I think people have mentioned is faster with Access but its not noticable.

Vince

[goatsucker]

It may be worth considering using an MSDE backend rather than a pure Access (Jet database) solution if there is any chance that you will go much over 20 users. MSDE is supposed to be optimised for around 10 users (like Jet, although I suspect it will perform better than Jet above this), but it gives you the option of seamlessly upgradeding to SQL Server. Belive me, it is a real pain having to maintain Access systems that have grown beyond 25 users.