[AccessD] Re: OT Quick Question

Robert L. Stewart rl_stewart at highstream.net
Wed Feb 25 10:44:00 CST 2004


UI - user interface

VBA - Programming language

VBA is not part of the UI, it is how the UI is
programmed.  Using VBA the way you said is
programming the UI.

By your definition, the UI is a subset of VBA,
not the other way around.  A form is VBA but
VBA is not a form.

At 10:12 AM 2/25/2004 -0600, you wrote:
>Date: Tue, 24 Feb 2004 14:00:40 -0600
>From: DWUTKA at marlow.com
>Subject: RE: [AccessD] Re: OT Quick Question
>To: accessd at databaseadvisors.com
>Message-ID:
>         <2F8793082E00D4119A1700B0D0216BF8022278E9 at main2.marlow.com>
>Content-Type: text/plain;       charset="iso-8859-1"
>
>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





More information about the AccessD mailing list