On Jun 30, 11:22=A0am, Rich P <rpng...@[EMAIL PROTECTED]
> wrote:
> Nothing is completely consistent and reliable. =A0In its prime days -
> Access was the most robust/consistent/reliable easy to use product on
> the market - far outperforming anything that was DOS based (like
> DBase3+, RBase, ...) -- But as cor****ate environments evolved around
> data centric paradigms - Access began to fall short - as you are
> experiencing. =A0If you want a significantly more
> robust/consistent/reliable system you need to step up to the newer
> generation of data management systems which would be the .Net
> environment.
I don't think Access ever outperformed DOS programs like FoxPro and
Clipper, nor ever could. A program that cares about the interface can
scarcely outperform a program that does not.
I have always maintained that I could deal with all the data needs of
the world with Clipper, DOS 2.12? and a twenty gig hard drive.
But Access gave us the Windows UI. And we liked that. And so Access
won us over. The fact that MS cajoled or bullied our clients into
using it may have had some influence as well.
But Access is NOT X-Base. For instance it lacks conditional indexes.
And to be efficient, it had to use the Rushmore technology, purchased
with FoxPro.
Today Access does not fall short; it is still a wonderful vehicle for
simple Database applications, especially if we can rid ourselves of
the nonsense found in sample dbs such as Northwinds, and verbose code
posted by MS and by many (but not all) its MVPs. (I never understand
about MVPs. Some are brilliant. Many are ordinary. And a few are drunk
[when they write or speak, at least]. I suppose they are just a cross-
section of the world.)
In the past few months I have been doing more and more .Net. I am not
sure that it is superior to COM applications. But it is newer, and is
something new to sell; selling is MS's chief job. Maybe I'll get to be
convinced as I use it more and more. But right now I'm skeptical. It
does too many things for me, things that I want to do, and control,
myself.
Ninety per cent of the quality of any application rests on the skill
and industry of the Developer. If one is having trouble with Access,
it's unlikely that changing to .Net will cure anything. But the OP is
not having difficulty. He/She asked a very legitimate question about
application roles which reflects both knowledge of Access and
capability. I'm not sure how .Net will help with Application Roles; I
suppose it's easier to control connections with .Net than with Access,
but I've never examined this and so can't be sure.
I don't think the .Net environment is a Database Manigement System. of
course, it may interface with Database Management Systems.
|
