Multi-user app. NO SERVER. Access Front, SQL or MSDE back??

[OrlandoG7]

Hello.

I've been asked to develop a 3 to 5 user Access db. There will be no server ($$$). The database needs to be hosted on the fastest computer (DELL P4, 256RAM, WIN2K Prof) and still be used as a desktop.

The database will be relatively simple, it'll have 50-100 new customer records added per month. There will not be much information to store and not too much functionality.

I'm afraid that as the database grows in size, it will slow down the host computer and load slower over the network. Is my assumption correct? I've heard that if I were to use Access Projects and point to an MSDE backend, it will run as a service on the host computer minimizing the computer's work load. I've also heard that it will allow quicker loading on the other desktops. Or is the SQL backend the way to go? However, because of the project's low budget, the SQL db would have to run on the above DELL desktop (WIN 2000 Prof) also.

I've read microsoft's documentation on these subjects but unfurtanetely I haven't been able to understand what the best solution for this project might be.

Any personal insight or sugestions would be tremendously appreciated.

Thanks
Orlando

 

[Junior1544]

if it's going to be that small, i would suggest going with a split access database... that's what i have, and my backend has over 7000 records in the main table... all you do is make all the tables in one mdb, and every thing else in the front end, another mdb... then link the tables... enjoy

--James JHauge@jmjpc.net
Life is change. To deny change is to deny life.

 

[OrlandoG7]

James: Thanks for the feedback. Is your app running on a dedicated server or on a user's desktop?

 

[Junior1544]

it runs off of my desktop... the only thing, the first person in in the morning turns on my pc, then goes about what they do, and the last person out, shut's it down...

--James JHauge@jmjpc.net
Life is change. To deny change is to deny life.