[AccessD] Future of Microsoft Access

Stuart McLachlan stuart at lexacorp.com.pg
Tue Jul 27 21:14:09 CDT 2010


 But I don't want a .Net based Access.   I want a standalone application that doesn't need a 
huge framework.


-- 
Stuart

On 27 Jul 2010 at 21:53, jwcolby wrote:

> Because Access was written in Assembler (the original product) and
> then C / C++.  We start with C# plus the framework.  We have ADO, we
> have forms, we have controls, we have all of the stuff that C# / .net
> framework give us.  The Access team had to write all of that stuff
> from scratch.
> 
> John W. Colby
> www.ColbyConsulting.com
> 
> 
> Mark Simms wrote:
> > John - I don't understand why 75% of the work would be done already
> > ?
> > 
> >> -----Original Message-----
> >> From: accessd-bounces at databaseadvisors.com
> >> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> >> Sent: Tuesday, July 27, 2010 9:38 PM To: Access Developers
> >> discussion and problem solving Subject: Re: [AccessD] Future of
> >> Microsoft Access
> >>
> >> Unless of course you used C# to create it.  Then about 3/4 of
> >> the work would be done already.  So that would only leave 10
> >> man years.
> >>
> >> ;)
> >>
> >> John W. Colby
> > 
> > 
> -- 
> 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