As the others have pointed out, you are dealing with two separate issues:
Stability
Security
These are two complete different and un-related issues.
When speaking of "lack" of ms-access security, the main problem occurs when
you use ms-access as a file share (a JET file share). Since each user
actually needs physical access to the data file, then users can copy or
examine the data base. You can, and should as a general rule hide all of the
ms-access interface. In fact, you can hide the ms-access interface to the
point where users generally can't look at or see the actual tables. In fact,
with no code you can hide all of ms-access to the point where users don't
even have to know it is ms-access. However, with a file share..users can
still copy the data file...and thus walk away with the data.
So, for high security applications, you can continue to use ms-access, but
the data store needs to be sql server (ms-access works as a fine client to
sql server). So, you can get all of the benefits of stability, reliability
and security if you use sql server for you data store...and simply use
ms-access as the front end.
As for stability?
I can say that if you run a split database, and always give each user a mde
file, and ensure that office updates are installed for ms-access and JET,
you can get a VERY reliable setup. I had ZERO complaints from my many
clients in terms of stability. I consider ms-access to be very stable in
this regards.
So, the issue is not that you can't use ms-access for the enterprise, but
not to use a JET file share if you need high security. (again, two different
issues here).
There are companies who have 1000 clients using ms-access all connected to
sql server. I think if you can have a 1000 users at the same time..then I
don't think this eliminates using ms-access in the enterprise role at all.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com http://www.attcanada.net/~kallal.msn