Re: VB in Access
- From: "Bob Butler" <tiredofit@xxxxxxxxxxx>
- Date: Wed, 7 Mar 2007 09:12:10 -0800
"scenic_man" <zcukpkn02@xxxxxxxxxxxxxx> wrote in message
74CHh.9185$kf.4960@trndny02">news:74CHh.9185$kf.4960@trndny02
[If this is the wrong newsgroup, please direct me to the correct
one(s). Thanks.]
What is the difference between VB as used in Access and VB (or
VBscript) not used in Access?
I've used VB (or is it VBscript?) in Access before,
but I have no idea how that relates to other implementations /
dialects.
There is VB which allows you to write code and compile it to an executable
There is VBScript which allows for creating "macros"; it's a subset of the
language and doesn't support forms or controls and only supports Variants
There is ASP which is similar to VBScript except you get the Request and
Response and other IIS objects instead of the WScript object
There is VBA (VB for Applications) which is what you have in Access and
other Office products; it has the specific application object model
available to it plus it has it's own forms and controls (which are not the
same as the ones that come with VB)
The various flavors overlap quite a bit; there's a core syntax that is
common to them all and then each adds on it's own extensions.
There is also VB.Net and VB 200x which are new MS products that have
essentially nothing in common with VB except for the name despite MS
marketing to the contrary.
--
Reply to the group so all can participate
VB.Net: "Fool me once..."
.
- References:
- VB in Access
- From: scenic_man
- VB in Access
- Prev by Date: VB in Access
- Next by Date: Re: VB in Access
- Previous by thread: VB in Access
- Next by thread: Re: VB in Access
- Index(es):
Relevant Pages
|
