Can I use an Access database for this ?

[LAURENS]

Hey there,

I have to write a relatively simple app. in Vb. Only 2 people are allowed to modify data in it. There will be about 200 people allowed to browse the data.

Will this be too heavy a burden for a MSAccess database (Access '97 using DAO350) ?

I know MSAccess can take about 10 concurrent users without breaking down, but does this also apply for browsing only ?

Regards,

Laurens (VB6 SP3)

[MrShickadance]

Well, the database it self is just a file... It doesn't carry any "load" ie the database doesn't have any executable data. As long as the server which the database lives on can keep up with the traffic, you can have as many users as you want.

[Nitro]

From personal experience, I don't think there will be a problem at all.

Access database only becomes unstable when you have way too many tables and queries. Therefore, as a developer, you should use VBA to create temp tables and drop it afterward.

To create temp tables use "Select Into".

[LAURENS]

With due respect....

Access can't take as many concurrent users as you like (unless you don't like many users). The official max. number of concurrent users is 255. Of the record Microsoft says that with more than 15 concurrent users doing update requests unpredictable results may occur (using the JetEngine, I should have mentioned that).

I was just wandering if many users just READING the database through Jet will cause problems.

I quote:

While Microsoft Jet is consciously (and continually) updated with many quality, functional, and performance improvements, it was not intended (or architected) for the high-stress performance required by 24x7 scenarios, ACID transactions, or unlimited users, that is, scenarios where there has to be absolute data integrity or very high concurrency.

My experience is that with about 20 users you won't have any problems provided you compress the database often (twice a week or so). Otherwise you will run into Corrupt database or Unrecognized database format messages.

[Crazy D]

Why not use SQL Server, or, it's free little brother, MSDE. That can handle more users then an access db can (and MSDE is free :-) Wow, something free from M$ ;-)

[LAURENS]

We've just decided on Oracle, so to me it's no longer an issue.

Thanks for the replies,

Laurens