[AccessD] .NET Access Replacement -- Was: Access doldrums??

Kenneth Ismert kismert at gmail.com
Thu Aug 5 15:11:08 CDT 2010


>
> John Bartow:
> MS VS LightSwitch - another attempt at replacing Access?
>
>
> http://www.eweek.com/c/a/Application-Development/Microsoft-LightSwitch-15-Re
> asons-NonProgrammers-Should-Try-It-Out-321214/?kc=EWKNLEDP08052010A<http://www.eweek.com/c/a/Application-Development/Microsoft-LightSwitch-15-Re%0Aasons-NonProgrammers-Should-Try-It-Out-321214/?kc=EWKNLEDP08052010A>
>


Bingo! That's exactly what it is -- .NET, SQL Express BE, easy Table/Forms
building, and can scale out to the Cloud/Azure.

It sounds exciting -- the only thing that could kill it would be onerous
platform or software licensing requirements.

That's pretty close to what I was thinking about in an earlier post:

> I would rather get rid of the 20 years of dreck and outdated thinking, and
come up
> with a radical, simple, modern database front-end app based on current
best practice.
> You could program the foundation in .NET, and let users script it in
JavaScript, the
> lingua franca of the Internet.
> Such an app, if well-conceived, could put a lot of .NET programmers
out-of-work ;)

And indeed, the 'professionals' are complaining about the 'hobbyist' focus
of LightSwitch in the responses to this blog post:
http://blogs.msdn.com/b/jasonz/archive/2010/08/03/introducing-microsoft-visual-studio-lightswitch.aspx

-Ken



More information about the AccessD mailing list