[AccessD] Re: OT Quick Question

Jim DeMarco Jdemarco at hudsonhealthplan.org
Tue Feb 24 14:45:07 CST 2004


I don't know if the mention of UI in these posts has to do with my post but I just want to clarify that I meant "designing user interface" in general as opposed to learning/using Access UI.  I know this is not just an Access issue but sure has a lot to with an application's success.

Jim D.

-----Original Message-----
From: DWUTKA at marlow.com [mailto:DWUTKA at marlow.com]
Sent: Tuesday, February 24, 2004 3:01 PM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] Re: OT Quick Question


Um, yeah.  Kind of what I was saying!

Technically, whether people like it or not, if you use a form, you are using
VBA, because Forms are Class Objects.  Whether you put code behind them or
not, they are still using VBA.  VBA can be used with the UI, for reasons
other then business rules.  In fact, the first VBA code I ever used was to
hide the Access Window, something that you can't do without VBA, and also
part of the UI.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Robert L.
Stewart
Sent: Tuesday, February 24, 2004 12:24 PM
To: accessd at databaseadvisors.com
Subject: [AccessD] Re: OT Quick Question


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


-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list