Re: MsAccess to SqlServer: sp_setapprole problem

I started out in this business as a younster fresh out of college with
Dbase3+.  When Access came out - it was revolutionary!  It still is a
great product, but the sphere of influence has diminished - depending on
the usage.  For example, I am a member of a flying club which uses an
Access2000 DB to manage stuff.  I was approached about stepping the
system up to sql server/.Net.  But since our system is basically single
user with no web interaction (we have a website but fairly static) I
decided that sql server/.net would be overkill and not worth the hassel
of maintaining.  But for large scale operations of a cor****ate business
with 1000s or more clients and a lot of data manipulation/web ops,
scheduled stuff, multiple users, Re****ting... the Access paradigm is not
robust enough, not consistent enough, lacks flexibility... Thus, the new
(newer) generation of data management came out -- .Net.  

Granted that Access is still the big money maker because it can be used
by a significantly wider range of users than .Net since you don't have
to be a programmer to use Access where .Net requires not only a
programming background but an OOP programming background.  This narrows
the market considerably.  But like Access, .Net is still much easier to
use than Java.  So, for Cor****ate level Rapid Application Development
(RAD), .Net is pretty hard to beat.

Rich

*** Sent via Developersdex http://www.developersdex.com
***