[AccessD] What problems converting A2K3 mdb to A2K7?

It doesn't while I'm writing code.  They have pretty much left the IDE
alone.  Designing UI, though, leaves me hunting for such simple items as
Save, which drives me nuts.  You want to format the text on a control,
say change the font?  You have to be in the right ribbon to do that.
Yes, human beings can adapt to nearly anything, but we work best with a
relatively stable environment.

Charlotte Foust 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Thursday, August 30, 2007 8:07 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] What problems converting A2K3 mdb to A2K7?


I have to disagree.  Perhaps if we'd all been weaned on Macs, we'd like
it, but then I never liked the Mac's "intuitive" UI either.  The ribbon
is the next logical step from personalized menus, which I also hated.
With the kind of confusion personalized menus tended to cause, you'd
think they would have thought long and hard before dumping the ribbon on
us, but I doubt that they did.  Now you see it, now you don't is great
for stage magicians but not for software developers.

==========I don't care for personalized menus either. As for the
developer issue -- as much as we all love Access as a developer's tool,
the truth is, MS doesn't market it that way. Love it or hate it, we're
kind of stuck with it. 

As a developer, why don't you like the ribbon -- how is it impacting
your work in a negative way? 

Susan H. 

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com