>"Brooks, Ruven" <[EMAIL PROTECTED]>
>3. EUP is about light weight, "quick and dirty" problem solving.
>... even when the practitioner possesses considerable skill in conventional
programming tools, they may choose not to use them because of the overhead
associated with them.
One interesting spin on this - Microsoft have three similar languages
VB (Visual Basic) - full-blown development capable of producing standalone
executables
VBA (Visual Basic for Applications) - very similar, including a similar
environment, however some differences in the language and cannot produce
standalone executables. Provides macro abilities in applications.
VBScript (Scripting edition) - "simplified" version can only be used in the
context of a scripting host, such as Intenet Explorer. No development
environment necessary.
(actually there are lots of variations on these - VBA in Access has different
behaviour in earlier versions of Access, for example, and each application
provides its specific object model which can be incorporated in other
applications - power of objects).
OK - I want to solve a problem. Will I use VBA in Excel (spreadsheet) rather
than VB? Will I use VBA in Access (database) rather than VB? What determines
my choice if all the tools are available?
Some of this comes down to ease of geting help, or if the solution is tied
very closely with the application. For example, my current timesheet is a
spreadsheet with a little code behind it - serves my purpose. My expense
tracking system is actually a couple of forms + code in a database - but will
move to a vb application soon.
VBScript is usually a non-runner, although I have to do some for work!
----------------------------------------------
Ron Newsham - Armillary Ltd
