[AccessD] Observations on AC 2007 (not good)

Hi Mark,
 
1. Forget Access, switch to .NET (VS2008 / VS2010) :) (conversion
VS2003->2005->2008->2010 worked smoothly for rather large projects here).

2. I have been working with MS Access since v.1.0 in quite some advanced
projects and I have got through conversions of small and large projects both
my own and legacy ones from

Access 1.0(1.1)->2.0->(95 skipped)->97->2000->AccessXP->2003->2007

It was always a PITA to make conversions (sometimes event RPITA :)) but it
was always doable.
Of course when one gets a legacy MS Access app and tries to fix it and in
the same time to support MS Access 2003 and MS Access 2007 versions of the
same legacy app that would be an RPITA^3 but if

- one is a masochist (I have been like that I must admit, I do hope I did
overcome this disease) and
- client has money to pay for "masochistic exercises" then there is no
reasons to complain about MS Access inadequacies :)

A kind of kidding of course, just wanted to share my experience with MS
Access apps support and conversion - all depends on time and money - if your
client doesn't have money - explain them that there is no miracles in this
world and escape them if they will not understand you - they will never find
solution for their problems whatever great MS Access developers they will
find...

Thank you.

--
Shamil
 
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms
Sent: 25 ?????? 2010 ?. 23:14
To: 'Access Developers discussion and problem solving'
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