[AccessD] Poll on Access 2007

Hi Max,

Yes, I understand, and I have seen the problems that many people have had in 
adapting to change, and recognising the value of the fantastic changes that 
were given to us with Access 2007.

I anticipate that in 10 years, my work will still be centred around Access 
development.  Maybe yours will be too.  If so, it is my fervent hope that we 
will look back at this period, and feel gratitude to the Access team at 
Microsoft, for their willingness to take the hard and unpopular decisions in 
order to keep Access current with the IT industry, create a product that is 
unique in its scope of functionality, and provide Access with a future.

We have to see Access 2007 as the first tentative steps in a major movement 
towards Access 2010 and beyond, and sometimes tentative steps only make 
sense in retrospect.  But I don't think there is any secret about the fact 
that Microsoft is investing hugely in the future of Access, and I have a 
hunch they're getting it right.

Regards
Steve


--------------------------------------------------
From: "Max Wanadoo" <max.wanadoo at gmail.com>
Sent: Saturday, June 27, 2009 7:09 PM
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] Poll on Access 2007

> Steve FWIW, I am definitely PRO MS but anti Access 2007.
>
> Over the years MS has given the majority a stable site of platforms which
> enables collaboration at various levels throughtout and across the World.
> It has never been Un-Affordable although it must be said that costs were
> never reduced once R&D and Profits Targets were reached - it would have 
> been
> nice to the old-2-back versions at half price for those who didn't want
> cutting edge.  But for me, MS has been a good thing.
>
> What I dislike mostly about A2007 is that, in real development terms, it 
> has
> bought nothing to the table.  It has remove interfaces that have, in some
> cases, taken years to hone and perfect, and all for the God "Looks".  It 
> is
> functionality and benefits that count and these are beyond the scope of
> end-users - complex, behind the scene coding has to be done to make it
> "perform" in a real tough business sense.  EG. What did the Ribbon bring 
> to
> the table for a developer producing a MR2 manufacturing solution?  Answer: 
> a
> lot of heartache to re-write existing code for no other reason than the
> interface has changed.
>