[AccessD] FW: Access 2007 (and other rants)

...but as a consultant I don't have to fight that battle ...small business 
owners don't give a hoot what tools I use as long as I can make it do what 
they want :)

...not doing that 9-5 crap ever again ...rather starve ...which is of 
course, always possible :)

William

--------------------------------------------------
From: "jwcolby" <jwcolby at colbyconsulting.com>
Sent: Friday, April 25, 2008 9:31 AM
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] FW: Access 2007 (and other rants)

> Because "real men don't use VB.net".
>
> Or because company executives are ignorant and believe that "real men
> don't code in vb.net" and so won't hire you unless you code in c#.
>
> Microsoft themselves will tell you that both languages are a thin veneer
> over the .net framework, both languages call into the .net CLR to do
> everything and the actual differences between the two languages are
> extremely minimal.  That said, c# can do a few things that vb.net
> cannot.  OTOH vb.net can do a few things that c# cannot.
>
> In the end, the "VB is a toy" is so deeply ingrained in the corporate
> culture that it really isn't worth fighting.
>
> If you make the switch though you will (potentially) earn twice the
> hourly rate since c# is a REAL man's language and everybody knows you
> have to pay real men more.
>
> ;-)
>
> Hewson, Jim wrote:
>> William,
>> Why did you move to C# instead of staying with VB?
>> I've attempted to "read" C# code and it really doesn't make sense to me.
>> It could be that I'm not accustomed to it.
>>
>> Jim
>> jhewson at nciinc.com
>>
>>
>> -----Original Message-----
>> From: accessd-bounces at databaseadvisors.com 
>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William 
>> Hindman
>> Sent: Friday, April 25, 2008 8:08 AM
>> To: Access Developers discussion and problem solving
>> Subject: Re: [AccessD] FW: Access 2007 (and other rants)
>>
>> ...I tried both Iron Speed and CCS as code generators and wound up 
>> throwing
>> them out in favor of coding it myself ...just too many compromises and
>> restrictions for me ...I wasn't willing to settle for what they put out 
>> and
>> thus spent as much or more time customizing their code than if I'd just 
>> done
>> it myself ...the real productivity tool for me was finding some really 
>> good
>> net resources and then building my own code library ...once that was in
>> place, I could really start using the huge variety of tools in the .net
>> framework where a simple one liner can bring a lot more results than you
>> could ever dream of in Access.
>>
>> ...I will make one comment though ...I knew AccessD was invaluable to me 
>> in
>> learning and working with Access ...but it wasn't until I got into 
>> asp.net
>> and c# and found no similar resource community that I realized just how
>> valuable it truly was and remains even now ...don't know why that is but
>> I've looked all over the net for more than a year now and just not found 
>> the
>> equivalent ...not even close.
>>
>> William
>
> -- 
> John W. Colby
> www.ColbyConsulting.com
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>