Confused about VB and VBA help.

[sanganaksakha]

Hi,

When I press F1 key inside VBA IDE, I’m taken to the VB help and not VBA help.

Now is everything shown in this help is available in VBA? Not as far as I know.

Everything in VB is not available in VBA.
So, shouldn’t I be seeing VBA help instead of VB help.

Or am I missing something here.

- Sanjay Kulkarni.

[Ed__Jobe]

No, you're not missing anything. That's the way it is. I've never had a problem with it. But like any documentation, nothing is perfect. If you have any concerns about accuracy, go to www.msdn.com for the latest info.

[dgorsman]

It *says* Visual Basic help, but its all for VBA. I haven't found anything in the help that is *not* applicable to VBA, and I haven't found anything in there that is specific to VB only. Care to provide some examples?

[Anonymous]

If you hit F1 when parked over a VB/VBA function that is applicable to all
VB/VBA forms, e.g. the .Show method, it pops up Visual Basic Reference.
Then, if you search in it for an AutoCAD specific feature, such as the
.GetPoint method, it doesn't find anything. But if you hit F1 when parked
on an AutoCAD specific feature, it opens the "AutoCAD ActiveX and VBA
Reference" Help. So you have to have an idea of where the feature you are
interested in lies, generic VB/VBA or application specific. It annoys me
sometimes too. I think that may be what the OP is referring to.


wrote in message news:5648239@discussion.autodesk.com...
It *says* Visual Basic help, but its all for VBA. I haven't found anything
in the help that is *not* applicable to VBA, and I haven't found anything in
there that is specific to VB only. Care to provide some examples?

[Anonymous]

"Visual Basic for Applications (VBA) is the language used to program in Visual Basic (VB). VB itself is a development environment; the language element of that environment is VBA."
"The VBA language (with a very few minor exceptions) is the same whether you're programming within VB or creating an application in a hosted VBA environment"
from "VB & VBA in a NUTSHELL" by Paul Lomax

[dgorsman]

Good point. Although I do like the separation between the AutoCAD object model and the VBA language reference - duplicated information quickly gets unsynchronized.

[sanganaksakha]

Thanks for all the answers.

I should have been more specific. I was talking about things specific to VB / VBA and not AutoCAD.

For example, while the following code works perfectly in VB6:

Sub main()

Load Form1

Form1.Visible = True

End Sub

similar code in AutoCAD VBA:


Sub try()

Load UserForm1

UserForm1.Visible = True

End Sub

Results in ‘Compile error - Function or interface marked as restricted, or the function uses an Automation type not supported in Visual Basic.’.


Its no big deal. But it is annoying and confusing. Unnecessary time may be wasted in finding out what works.

It would have been better if what works in VBA had been explicitly mentioned.

Its about user-friendliness and not about any technical point.

- Sanjay Kulkarni

=========

[Anonymous]

that is one of the anomalies between the two environments. forms in VB are
called Form1 and UserForm1 in VBA. most developers don't use Load (...) but
instead use Form1.Show and UserForm1.Show respectively. By and large the
Visual Basic language is the same between the two environments.

joe ...


wrote in message news:5650023@discussion.autodesk.com...
Thanks for all the answers.

I should have been more specific. I was talking about things specific to VB
/ VBA and not AutoCAD.

For example, while the following code works perfectly in VB6:

Sub main()

Load Form1

Form1.Visible = True

End Sub

similar code in AutoCAD VBA:


Sub try()

Load UserForm1

UserForm1.Visible = True

End Sub

Results in 'Compile error - Function or interface marked as restricted, or
the function uses an Automation type not supported in Visual Basic.'.


Its no big deal. But it is annoying and confusing. Unnecessary time may be
wasted in finding out what works.

It would have been better if what works in VBA had been explicitly
mentioned.

Its about user-friendliness and not about any technical point.

- Sanjay Kulkarni

=========