Is Access horrible for my database???

[latestgood]

I am trying to create twenty user database. This database is used for employees to enter their budget. In theory we should have about 10,000 records max. Some people told me that I shouldn't use Access with msSql because Access is not reliable. However, I like Access because of customization and easy maintenance. Is Access so unreliable that I shouldn't use it? We have the resources to buy more expensive programs but we really like the fact that we can customize Access.

Thank you,

[June7]

I have project that has many more records than you expect in yours but it is not linked to msSQL. My backend is another Access file. I have 9 users (usually 3 or 4 at a time). Everyone is comfortable with the interface and Access does everything we need. No major issues encountered in 3.5 years now. However, if users try to edit same record, will get conflicts message and one user's edit will not save. This has happened maybe twice. Some large, complex forms (with subforms) and reports with graphs can load rather slow but we find it tolerable.

[latestgood]

June,

Wouldn't it be better for you to use free version of MSsql to solve speed issue and two users trying to edit at same time?

[June7]

I started to explore that possibility about a year ago, even downloaded software but ran into setup issues and gave up. I don't know anyone locally using msSQL I could get with for assistance. As you pointed out, Access is easy to customize and maintain. Also, don't know if the form and report loading would be any faster. Would still be a split design with linked data. Users don't hit same record often enough to worry about, like I said, maybe twice in 3+ years.

[rpeare]

I'm with june if you only expect 10000 records that is a very small load for Access. I've got some databases with literally hundreds of thousands of records and don't have any issues. As long as you don't have more than about 3 - 5 concurrent users (or users that are likely to be modifying or adding records at the same time) you should be fine. The worst case scenario is that if you have 20 departments you give each department a subtable where they can enter their budgets then have some other process running in the back ground that adds all the new information to a combined table after business hours. I haven't ever run into the need to do this, but I've never had the possibility of 20 users on a single db.