[AccessD] What is .Net - was Access/SQL

But that's what I currently do all the time!   I often need to use *more*  that  two differenent 
languages in a single project.  It's not unusual these days for me to need four.  In the 
majority of cases, Access is one of those components.  I don't have a problem with this.  It's 
just that I don't need .Net to replace one or more of the other components.

:-)

-- 
Stuart

On 14 Nov 2009 at 17:24, jwcolby wrote:

> If you have ever read about the architecture of .Net, the language is a very thin veneer over the 
> framework.  Each language is slightly different and as of now, each language exposes a handful of 
> things that the others don't.  That means that (for now) C# can do a few things that VB cannot, but 
> VB can do a few things that C# cannot.  However... you can use BOTH in the same project so if you 
> have a language preference but absolutely need the capabilities of the other language(s) then use 
> them where needed.
> 
> Try doing THAT in Access.  Access is without par in what it does, but it has definite limitations 
> and weaknesses, and to try to claim otherwise or cover them up does a disservice to everyone.
>