Carolyn Johnson
cjlabs at att.net
Thu Nov 25 14:55:30 CST 2010
I'm actually happier with 2007. I have a workaround for the ribbon so that 2007 uses my custom toolbars instead (and works in 2000/2002/2003). But that method is NOT working in 2010. Plus, 2010 seems to have a bug that causes extra pages to print in a report (header on a blank page), where they do not in 2000, 2003 or 2007. Carolyn Johnson ----- Original Message ----- From: Mark Simms To: 'Access Developers discussion and problem solving' Sent: Thursday, November 25, 2010 2:13 PM Subject: Re: [AccessD] Observations on AC 2007 (not good) Unfortunately, my two clients are mandating operation in BOTH 2003 and 2007 versions: Brutal, simply brutal. Once again, Microsoft's mindset of strategically pulling AC2003 run-time off the shelves so that users are forced into AC2007 just makes matters worse. They effectively cut off the legs of AC developers....that's US ! > > I started converting a project from AC 2003 to AC 2007 but > ran into so many issues that I told the client that 2007 was > not worth and it would be a good savings in the long run to > jump right into 2010. Never having used 2010 it was a bit of > a jump of faith but I thought how much worse could it be. It > was a good choice. > > I believe the 2007 should be avoided at all costs, just like > the OS (a name that must not be spoken) and move straight to > Win7 or in our case Access 2010. > > Thanks for the your warnings and investigations. Do not > hestitate to post any of your other finds. > > Jim -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com