The question of how many users, and the issue of having to re-write are not
related at all.
There are ms-access appcltions out there with 1000 users (at the same time).
So,really the only limits you will encounter is what data engine you use.
If that mde application connects to sql server, then the only limits in
terms of number of users will be the limits of that database engine you use
(That engine can be Sql-server, oracle etc. etc. etc.
So, there is NO reason to bring up the issue of having to re-write the
application when you reach a certain number of users. For sure, it is
sensible to ask what the limits are of a particular data engine you use with
ms-access. ms-access is not the data base, but only a visual basic
development system like C++, or VB or whatever. Just like VB, you write code
and forms. That code and forms connects to a data source. So, the key, or
important question here is what is the data source you are going to use.
However, for general 2-tiered applications, the number of fusers is not
going to be ANY DIFFERENT between VB, c++, or ms-access (they are all just
software development tools) (again, I repeat: THERE WILL BE NO DIFFERENCE IN
performance between the 3 platforms). So, I am at a loss to why you asked
about re-writing...as the limits between these tools are not any different
in the above case.
If you are using the JET engine as a file share, then the theoretical max
number of users is 255. However, in practice, 1-20 users is a comfortable
range. Some have stretched the number into the 100's, but I would not
recommend such a high user count. Also, most issues of how many users will
actually revolve around how well the application was designed. We often hear
of applications that are to slow with 1 user..so how can one expect 5 users
in that case!
As mentioned, you can also use any server type based engine with ms-access.
So, we are talking sql server here. When you use a server based system, then
the limits on the number of users is going to be whatever you spend on that
server!
