[AccessD] 10 things I don't miss about Access

Jim, you must have been reading my diary again. :)

Susan H.
>
> And I do think your right; Microsoft is sliding Access towards the 
> end-user
> end of the scale.  We here all know it's much more then that, but it 
> always
> has been marketed as an end-user tool and Microsoft seems to be focusing 
> on
> that once again.  Last couple of releases have been focused on simplifying
> things and adding end-user features rather then anything for developers.
> And long standing developer problems are simply not being addressed.
>
> What I see happening is Microsoft moving away from VBA for all of Office.
> Access developers will be either pushed into VS or Lightswitch, which will
> become Microsoft's light weight/RAD app development tool.  Access may or 
> may
> not remain in Office, but if it does, I think it will become a much 
> simpler
> product.
>
> And before everyone gets up in arms about the "light weight" comment 
> above,
> I do understand that you can do a wide range of things with Access and I 
> do
> love it for that.  But it does have some serious limitations.  Access
> developers have been ingenious over the years in working around a lot of
> those limitations (i.e. lack of third party controls), but it has two
> serious problems that nothing can be done about; corruption and 
> sensitivity
> to its environment.  The latter is more of a reference to VBA and
> references, but how many of us have dealt with app install issues with
> either the full or run-time version?  Or multiple versions on the same
> machine?  If I asked those questions in a room full of developers, I bet 
> you
> just about every hand would be raised.