AW: [AccessD] Vba and Office

Alun,

I work almost exclusively in C# now. It is not without 
it's quirks and drawbacks, but overall I'm very impressed 
and pleased. Once you get past the initial learning curve, 
its Good Stuff. That is, of course, my opinion, and no 
doubt others here will disagree.

Another player in my shop has settled on vb.net, and she 
is finding the transition more painful that I did for my 
leap from VBA to C#. Maybe its because I was learning 
syntax as well as the .NET way of doing things and so 
expected nothing to transfer. When my previous knowledge 
did transfer, even a little, it was a pleasant surprise. I 
think she's fighting with expectations that aren't panning 
out as well as she'd hoped.

My own question on this subject: is there any reason at 
all to make a move to C++.net? From where I sit, it looks 
like another steep learning curve for comparatively little 
gain. My understanding is that with C++ you can have finer 
control over some things but at the cost of giving up 
managed code... that seems like an unwise choice unless 
(one of my favorite phrases) there are compelling reasons 
to do so. Any thoughts?

Ron


On Fri, 17 Oct 2003 16:24:12 +0200
  "Garraway, Alun" <Alun.Garraway at otto.de> wrote:
>hi John,
>
>Already started (vb.net), through .net have started using 
>classes in access
>so its worth the effort for me....
>
>question: are going to vb.net or c#?
>
>alun
>
>-----Ursprüngliche Nachricht-----
>Von: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com]Im Auftrag 
>von John Colby
>Gesendet: Freitag, 17. Oktober 2003 14:18
>An: Access Developers discussion and problem solving
>Betreff: RE: [AccessD] Vba and Office
>
>
>...VBA programmers should face the facts and take the 
>VS.NET plunge.
>
>And do it NOW.  VS.Net is not the smallest learning curve 
>I have ever faced!
>
>John W. Colby
>www.colbyconsulting.com