Client/Server application design

[Waldi]

I new to Acess and working on designing front end multi client application (client/server) based on Acess using MS SQL server database. I am looking for recommendation on what is the most efficinet way of doing so. I will have fairly small number of concurent users (3-5) and average load/data entry. Should I use linked table approach or Access Data Project?
You opinions will be greatly appreciated.

 

[SydneyGeek]

You'll need to ask yourself several questions regarding the multiuser scenario before you get the right answer.
For example, if you already have the data in MS SQL, you'll need some sort of client / server approach. If you haven't built anything yet, and you don't envisage going beyond about 5 or so concurrent users, a split Access database may be all you need.
There are some good books on the topic -- two that I know of are
Access 2000 Developer's Handbook Volume 2: Enterprise Edition (Litwin, Getz & Gilbert), ISBN 0-7821-2372-4 and
Access 2000 Client / Server Solutions (Klander), ISBN 1-57610-417-6

Hope that helps

 

[Waldi]

Thanks for the advise. I decide to use SQL server and use Access ADO for front for clinet.

 

[Dugantrain]

That's a lot of ADO, partner. If you're looking/are being pressed to spit something out quickly, you may just want to link some tables to the SQL Server. It's won't be as robust or efficient as a client/server configuration, but it'll probably take about 5% of the time to develop.