Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsVB SyntaxEnterprise DevelopmentDatabase AccessControlsCOMWin APICrystal ReportDeploymentGeneralGeneral 2
Related Topics
VB.NET / ASP.NETMS SQL ServerMS AccessOther Database ProductsMore Topics ...

VB Forum / Database Access / October 2006



Tip: Looking for answers? Try searching our database.

vba to vb.net

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
DesCF - 25 Oct 2006 18:59 GMT
Is there a big learning curve in moving from vba to vb.net ?  Are there  
any resources that anyone would recommend ?

Signature

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Ralph - 25 Oct 2006 20:17 GMT
> Is there a big learning curve in moving from vba to vb.net ?  Are there
> any resources that anyone would recommend ?

There are very few comparisons between the two languages, beyond sharing
basic keywords, conditional statements, the fact they both use objects, and
you get to click the mouse a lot.

There is going to be a large learning curve to dotNet, period. A dotNet
language is only part of it - the Framework, new designers, new data access,
etc. will all have greater impact.

Whether or not knowing VBA before hand would provide any advantage would be
tough to measure - I'll guess, and give you a two-week headstart over
someone who has never seen any dialect of VB previously.

-ralph
DesCF - 25 Oct 2006 22:47 GMT
I suppose this isn't what I wanted to hear.  Is it really as bad as this  
anyone ?

>> Is there a big learning curve in moving from vba to vb.net ?  Are there
>> any resources that anyone would recommend ?
[quoted text clipped - 15 lines]
>
> -ralph

Signature

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Douglas J. Steele - 25 Oct 2006 23:00 GMT
You'd probably be better off asking in a newsgroup related to .Net, such as
microsoft.public.dotnet.languages.vb, but yes, there's a huge difference,
and a definite learning curve.

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)

>I suppose this isn't what I wanted to hear.  Is it really as bad as this
>anyone ?
[quoted text clipped - 18 lines]
>>
>> -ralph
Jan Hyde - 26 Oct 2006 08:43 GMT
DesCF <descf@aol.com>'s wild thoughts were released on Wed,
25 Oct 2006 22:47:41 +0100 bearing the following fruit:

>I suppose this isn't what I wanted to hear.  Is it really as bad as this  
>anyone ?

It's a new language, it's no more complicated than moving to
any new language. What can be confusing is that some VB
commands still work and are called in the same way but don't
work the same way anymore.

I really like a lot of what dotnet has to offer.

J

>>> Is there a big learning curve in moving from vba to vb.net ?  Are there
>>> any resources that anyone would recommend ?
[quoted text clipped - 15 lines]
>>
>> -ralph

Jan Hyde (VB MVP)

Signature

Uphill: Oral medication for adults (Stan Kegel)

Ralph - 26 Oct 2006 14:06 GMT
> I suppose this isn't what I wanted to hear.  Is it really as bad as this
> anyone ?

I would like to echo Jan's comment. I perhaps did give the impression that
dotNet was complicated. I was merely addressing the issue of whether prior
VB experience would be of any help in the "learning curve".

Programmers often use "language" when they are actually referring to a
"development environment" or "platform". A programming language is merely
the encoding we use to provide instructions to create something. Almost all
languages can be 'learned' in a week. Experience with any prior language
only improves your your ability to grok the next new thing.

The "platform" takes longer. The dotNet platform is huge compared to
anything you have run into with VBA. But it is 'learnable'. <g>

-ralph
DesCF - 26 Oct 2006 20:58 GMT
I eventually got round to posting in the right newsgroup and got this  
useful response
(My question was 'what is the difference between vb, vb.net, and vba?'):

They have been obfuscated to an extent by Microsoft, but broadly it is  
this.

VB is the name given to the older versions of Visual Basic, up to and
including VB6 which was released in about 1998.

VB.NET is the name generally given to more recent versions of Visual Basic
released from 2000 onwards, and which make use of the .net framework.
Although VB.NET is claimed by Microsoft to be an update to VB, they aren't
all that compatible and you should be wary about attempting to port any
project of significant size from VB6 to any later version.

The obfuscation creeps in because Microsoft calls the most recent version
"VB2005", dropping the .net suffix from the name even though it uses the
VB.NET syntax, not the VB6 syntax.

VBA (Visual Basic for Applications) is the version of VB that is included
inside various of the Microsoft Office applications, and is also licensed  
by
Microsoft for other companies to include within their own applications. It
uses the VB6 syntax and usually makes available a specialised object model
for controlling the host application, and has a simpler forms library than
VB6 (VBA UserForms are simpler and less capable than VB6 Forms).
General-purpose VB6 code can often be imported into VBA projects and work
unmodified.

> Is there a big learning curve in moving from vba to vb.net ?  Are there  
> any resources that anyone would recommend ?

Signature

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Jan Hyde - 27 Oct 2006 08:37 GMT
DesCF <descf@aol.com>'s wild thoughts were released on Thu,
26 Oct 2006 20:58:17 +0100 bearing the following fruit:

>I eventually got round to posting in the right newsgroup and got this  
>useful response
[quoted text clipped - 25 lines]
>General-purpose VB6 code can often be imported into VBA projects and work
>unmodified.

VBA doesn't use VB6, more like VB6 uses VBA (and more)

Take a look at a VB6 project and you'll notice it references
'Visual Basic for Applications'

VBA code often ports to VB6 unmodified in my experience
(can't say I've had much cause to do it the other way round)

>> Is there a big learning curve in moving from vba to vb.net ?  Are there  
>> any resources that anyone would recommend ?

Jan Hyde (VB MVP)

Signature

Where does mercury come from?

Hg wells!

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.