[AccessD] Known Bugs List in A2K7/10

I think this is fine *IF* 2010 is not going to flake out on your users after
deployment when you're all confident in your software cuz it worked fine in
development... I develop (the limited bit I do) in 2010 so that if it
doesn't work for me, I won't expect it to work for them. If something is
supposed to work, I don't see the benefit of gaining false assurance just
because it does in 2003. And I have definitely seen code I wrote in 2003 not
work in 2010, I just can't remember what just now.


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: Wednesday, October 19, 2011 4:29 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Known Bugs List in A2K7/10

I'm still developing primarily in 2003 and deploying the .mdbs on 07/10
installations.  
Generally it works seamlessly.

-- 
Stuart

On 19 Oct 2011 at 10:14, Gustav Brock wrote:

> Hi Mark and Darry and ...
> 
> Oh my, what a frightening thread. You guys and Charlotte really scare
> one from ever touching development in Access 2007 or 2010. I never
> moved beyond 2003 ... then took a sharp right (pun and pun intended!)
> turn to .Net, C#, and Visual Studio.
> 
> /gustav
> 
> 
> >>> darryl at whittleconsulting.com.au 19-10-2011 01:51 >>>
> Thanks Mark,
> 
> Looks like am in for some future 'fun'.  Right now I use A2007 80% of
> the time vs A2010 for the other 20%.  Perhaps my current experience
> and feelings are based on this ratio rather than the actual issues in
> each individual product.
> 
> I do find A2010 more finished and smooth to use, but that maybe
> because I don't push it around too much right now.
> 
> Let just say I respect your (and everyone on this list) opinions and
> happy to listen to the (usually excellent) advice you all give on
> these matters.
> 
> Cheers
> Darry.
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms
> Sent: Wednesday, 19 October 2011 10:08 AM To: 'Access Developers
> discussion and problem solving' Subject: Re: [AccessD] Known Bugs List
> in A2K7/10
> 
> No way. 2010 is way more pain than 2007. That being said, AC 2007
> could easily be blown-up by simply moving form controls on a multipage
> control. The sheer number of complaints about 2010 on the social.msdn
> website forum for Access is pretty much the proof in the pudding
> so-to-speak.
> 
> > I am with Doug, I prefer A2010 to A2007 which I find painful beast
> > to use most of the time. in-elegant and clunky is how I best
> > describe it - and freaking weird. It does some strange things from
> > time to time.
> 
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 



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