Re: Quick Question
- From: Yitzak <terryshamir@xxxxxxxxxxx>
- Date: Thu, 21 Feb 2008 05:46:40 -0800 (PST)
On 21 Feb, 12:32, "Albert D. Kallal" <PleaseNOOOsPAMmkal...@xxxxxxx>
wrote:
<learning_co...@xxxxxxxxxxx> wrote in message
news:540dbcbd-120d-4569-ab9e-d60969d83057@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
What is the difference between Visual Basic and Access XP VBA?
Thanks
The code syntax, and even apparently the same compiler is shared between the
two products. For the most part the syntax and use of the two languages is
nearly identical.
The most significant difference between the two products is access and
visual basic have a different forms object model. Considering that the bulk
of your applications are built around the forms model, then there is a
significant difference in the use of the two languages because you're
dealing with different object models. (so the language and programming
syntax is the same, but the development process between the two products is
significantly different because of different kinds of forms used).
For the most part it is a trivial matter to take code from visual basic and
move it into an MS access environment. I often take the VB6 examples from
the Internet and modify them for use with access all the time.
However, and this is a big however if that sample code uses the visual basic
form, then moving the code will be VERY difficult. As mentioned since so
much of the applications are built around the forms model, then there's a
significant difference in the use of the two environments.
Perhaps the most significant difference in the approach to developing data
centric applications is that MS access uses the concept of bround data
forms, and visual basic does not. for the most part this means that you have
to code and write and develop your own system of updating the data in a
visual basic form, or as an access all the dirty work is done for you.
if you're developing an application that's rich in data editing forms,
you'll find that you'll get about 3, perhaps 5 times as much work done for
the same amount of effort in using MS access over that of visual basic 6
forms.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKal...@xxxxxxx
Access VBA like other Office VBA is stuck in its own product.
If you are happy doing Access VBA and your back-end (where Data is
stored) is always going to be Access then stick with it - its going to
be far better for you.
However if you ever wanted to move data to another DB like Oracle/
MSSQL then VB IMO would be better. You can do this in Access via an
ODBC driver and link all tables to external DB - but you lose alot of
the nice features that make your life easy in Access.
VB is a standalone lang, that you can create your own applications
(exe files) together with code libraries (OCX, dlls). E.g those
controls you can stick on forms in Access - you could create your own
one in VB say a custom grid, compile into binary code (mygrid.ocx) and
use it in many environments that support COM/ActiveX e.g. other VB
apps, Access, Excel or Word etc etc.
.
- References:
- Quick Question
- From: learning_codes@xxxxxxxxxxx
- Re: Quick Question
- From: Albert D. Kallal
- Quick Question
- Prev by Date: Re: Why Same query results in two different # in SQL Server vs MS Access
- Next by Date: Re: Create a relationship in code
- Previous by thread: Re: Quick Question
- Next by thread: MS Graph (or equivalent)
- Index(es):
Relevant Pages
|
