Best VBA development environment

[J. McConnell]

My company has just accepted a VBA/Access project, though we have never
developed with VBA before. We are curious if there are many benefits to
developing in VB .Net instead of the VB Editor that is built into Access.
We currently only own C++ .Net and are wondering if buying VB .Net would be
worth it.


Thanks in advance for any info,

J.

 

[J. McConnell]

On Thu, 10 Jul 2003 22:24:10 -0600, in

microsoft.public.office.developer.vba you wrote:


-----Original Message-----

From: (e-mail address removed) [mailto:[email protected]]

Sent: Friday, July 11, 2003 6:19 AM

To: J. McConnell

Subject: Re: Best VBA development environment

If you want the least hassle, stick with the VB Editor built into

Access. Anything else you'll have translation issue to work out and

that includes VB6 and VB.Net.

Make sure you have MS Office installed and have the appropriat help

files that define all the objects: VBAWrd.chm, vbaxl9.chm,

vbappt9.chm, vbaoff9.chm.

And checkout the updates and patches on the microsoft office download


http://office.microsoft.com/productupdates/default.aspx

Thanks a lot, this is what I needed to know. Out of curiosity, what kinds
of translation issues? Removing stuff that's valid in VB but not in VBA?





Thanks,



J.

 

[Dave]

pls be careful, VB and VBA have alsolutely nothing to do with VB.Net, aside
maybe from the coding conventions but even this is purely cosmetic. If you
want to move on to the DotNet platform go with c# instead of VB.Net. The
learning curve will be the same if not shorter seeing as you already code
c++.

Porting VB 6.0 code to VBA modues and vice-versa is easier as the two use
almost the same syntax. There are some small differences but if you keep
your code generic enough its not a problem.

I'd strongly recommend using the vba editor supplied with ms access.

hth,
dave

microsoft.public.office.developer.vba you wrote:

to Access. would

-----Original Message-----

From: (e-mail address removed) [mailto:[email protected]]

Sent: Friday, July 11, 2003 6:19 AM

To: J. McConnell

Subject: Re: Best VBA development environment

If you want the least hassle, stick with the VB Editor built into

Access. Anything else you'll have translation issue to work out and

that includes VB6 and VB.Net.

Make sure you have MS Office installed and have the appropriat help

files that define all the objects: VBAWrd.chm, vbaxl9.chm,

vbappt9.chm, vbaoff9.chm.

And checkout the updates and patches on the microsoft office download


http://office.microsoft.com/productupdates/default.aspx

Thanks a lot, this is what I needed to know. Out of curiosity, what kinds
of translation issues? Removing stuff that's valid in VB but not in VBA?





Thanks,



J.

 

[Ty Anderson]

If you want to develop Office Apps (like COM Add-Ins) using .Net make sure
you are aware of the consequences of your language choice. There are some
key things to be aware of when choosing C# over VB.Net. In short, your
will write a lot more code when using C# instead of VB.Net. The main reason
for this is that C# does not support optional parameters and VB.Net does.
Optional parameters are a big part of Office.

Here is the best article out there that discusses this topic:

http://msdn.microsoft.com/library/?url=/library/en-us/odc_vsto2003_ta/html/OffCSharp.asp?frame=true

pls be careful, VB and VBA have alsolutely nothing to do with VB.Net, aside
maybe from the coding conventions but even this is purely cosmetic. If you
want to move on to the DotNet platform go with c# instead of VB.Net. The
learning curve will be the same if not shorter seeing as you already code
c++.

Porting VB 6.0 code to VBA modues and vice-versa is easier as the two use
almost the same syntax. There are some small differences but if you keep
your code generic enough its not a problem.

I'd strongly recommend using the vba editor supplied with ms access.

hth,
dave

microsoft.public.office.developer.vba you wrote:

My company has just accepted a VBA/Access project, though we have

never

developed with VBA before. We are curious if there are many benefits

to

developing in VB .Net instead of the VB Editor that is built into

Access.

We currently only own C++ .Net and are wondering if buying VB .Net

would

worth it.

Thanks in advance for any info,


-----Original Message-----

From: (e-mail address removed) [mailto:[email protected]]

Sent: Friday, July 11, 2003 6:19 AM

To: J. McConnell

Subject: Re: Best VBA development environment

If you want the least hassle, stick with the VB Editor built into

Access. Anything else you'll have translation issue to work out and

that includes VB6 and VB.Net.

Make sure you have MS Office installed and have the appropriat help

files that define all the objects: VBAWrd.chm, vbaxl9.chm,

vbappt9.chm, vbaoff9.chm.

And checkout the updates and patches on the microsoft office download


http://office.microsoft.com/productupdates/default.aspx

Thanks a lot, this is what I needed to know. Out of curiosity, what kinds
of translation issues? Removing stuff that's valid in VB but not in VBA?





Thanks,



J.