[AccessD] One Note

Jim Lawrence accessd at shaw.ca
Mon Jan 23 22:50:28 CST 2012


Blame the developers not the tools.

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Salakhetdinov
Shamil
Sent: Monday, January 23, 2012 2:12 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] One Note

Hi Gustav and Mark,

Yes, failure in converting an MS Access app into a .NET-driven one can't be
IMO a cause to blame .NET or Visual Studio...

Thank you.

Shamil

24 января 2012, 01:39 от "Gustav Brock" <gustav at cactus.dk>:
> Hi Mark
> 
> But don't blame .Net or Visual Studio for this.
> 
> /Gustav
> 
> 
> >>> marksimms at verizon.net 23-01-12 21:16 >>>
> Ah yes John...and that's the "big problem"....and this is likely the
reason
> my former client is moving towards litigation with the developer in their
> Access to DotNet migration and upgrade. It's been over 2 years now, and
they
> still have....nothing.
> 
> > Whereupon the kitchen sink is there by demand and you are not given the
> > option.  ;)
> 
> -- 
> 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




More information about the AccessD mailing list