CIS 56 INTRODUCTION TO VISUAL BASIC

Evening School

Assignment #2

Week of February 3, 2003 due by February 10, 2003

Your second programming assignment then, is as follows.

Like in the day school, you are to design and code an application that incorporates 20 unique features. Each feature being equal to 5 points

You are free to choose whatever you want to use. (Objects, Properties etc)

Directives:

Each entity you use, whether it be an object, a graphic, specific code etc can only be used ONCE. This does not mean that you can only use a specific entity once it means that each entity you use is considered one feature of the application. So, if you had a project that included 20 forms, the form object would be considered ONE feature, not twenty.

If you used a form and changed its name property, that would be considered a feature. Using the name property on another object WOULD NOT constitute a feature. Also, using a property of a different name that does the same thing as the property of another object WOULD NOT constitute an additional feature.

For example, if you set the Caption property on an object, setting the Text property on another object would be considered as one feature.

HINT: IF YOU STUDY THE CAPTION AND TEXT PROPERTIES, THERE IS A WAY THEY CAN BOTH BE USED AND EACH WOULD COUNT AS A SEPARATE FEATURE AND YOU DONT NECESSARILY HAVE TO USE CODE INCLUDES ADDITONAL PROPERTIES RE: THE TEXTBOXthink about it!!!!!!!!!

One of the key things here is UNIQUENESS.

No splitting hairs

The fact that different prefixes are used as the naming convention for an object does not constitute different features. You are still using the Name property. Also, the fact that some properties are Boolean does not mean that by setting them to True/False constitutes two features. So, setting one property of an object to true, and another to false is still only one thing.

In short, the features of one property dont count for more than one thing.

You are to document your assignment as per the directives in the first assignment.

Also, you must point each feature to me by using documentation. I would prefer it if each documentation for a feature be in all upper case letters and your application documentation be in the usual upper/lower case form. I wont be picky about this, just as long as I know your features.

Design time features can be listed above the option explicit.

Code features can be in the code section.

Example:

Design time features:

FEATURE #1 I USED THE NAME PROPERTY TO NAME MY

FORM, frmSecondAssign

Option Explicit

Code feature:

Private Sub Whatever_Click()

This procedure does this and that.

FEATURE #2 I AM DOING THIS USING THAT.

This.that = this is whatever: & val(those.these * .60)

End Sub

YOU MAY NOT USE THE FORM OR ANY NAME PROPERTY IN THIS ASSIGNMENT AS A FEATURE (S) BECAUSE I USED THEM.

You may add TWO additional features as spares along with your original twenty. If I find that one or two or your originals are not unique, I will draw on the spares and replace the non-unique ones with the spare(s) counting it/them as part of the twenty.

You must label the spares as SPARE OR SPARE #1 SPARE #2. This is irrelevant as long as I know they are spares.

With this, as with all assignments, feel free to ask me any questions via e-mail. If you are confused about any part or all parts of any assignment, please e-mail me.

Note: Class does not have to end at 9:40 on Monday. We can still communicate via the internet when you have questions or problems.