[AccessD] Re: OT Quick Question

Robert L. Stewart rl_stewart at highstream.net
Tue Feb 24 12:23:51 CST 2004


Drew,

VBA is not part of the UI.  And, since it is
used in Access, it would still be "strictly
done in Access."  VBA is what adds business
rule functionality into the UI for things
that the UI cannot do on its own.  For example,
you can set a control on a form to be required,
and do minimal validation of the data entered
into the control.  But, you can use VBA to open
a recordset or check many more values as a validation
of the data where you cannot do that from the UI
without VBA.

In order to implement a real application with Access,
you have to know VBA.  You have to house the business
logic somewhere.  And normally, in an Access application,
that is in the VBA code somewhere, either code-behind
or in modules.  If you do not use VBA, you simply have
a simple data entry system and not an application.

Robert

At 12:00 PM 2/24/2004 -0600, you wrote:
>Date: Tue, 24 Feb 2004 11:13:16 -0600
>From: DWUTKA at marlow.com
>Subject: RE: [AccessD] OT Quick Question
>To: accessd at databaseadvisors.com
>Message-ID:
>         <2F8793082E00D4119A1700B0D0216BF8022278E1 at main2.marlow.com>
>Content-Type: text/plain;       charset="iso-8859-1"
>
>Granted, but which UI's work the best, one's done strictly in Access, or
>ones that utilize VBA?  Sure, it may depend on the application itself, but
>VBA certainly provides a lot more capability.
>
>Drew





More information about the AccessD mailing list