CSCI 130 Visual Basic for Applications

Course Syllabus – Spring 2004



Dr. Bill Manaris


Room: 210 J.C. Long Building
Phone: (95)3-8159


Office Hours:

Mondays 11 a.m. – noon & 1 – 3 p.m., Wednesdays 1 – 4 p.m., and by appointment.  Feel free to come in with questions and problems you may have.  I may also be available for a few minutes after class.


A programming course using Visual Basic to access the programmable object libraries in productivity applications. Using a consistent integrated development environment, students will learn how to automate tasks and how to develop custom applications. Special topics covered include VB control structures, the object models, Active X controls, interface design, debugging and event handling.

Students are expected to be familiar with MS Windows.



Zak, D. (2001), MS Visual Basic for Applications, Course Technology, ISBN 0-619-00020-1.



Gleick, J. “Little Bug, Big Bang,” The New York Times Magazine, December 1, 1996. Also available online, as “A Bug and a Crash: Sometimes a Bug is more then a Nuisance”, (


Additional materials will be made available via handouts and online on the class webpage (



Course Objectives:

·         To comprehend fundamental capabilities of computing devices [2]

·         To learn and apply fundamental programming concepts [3]

·         To learn how to use an Integrated Development Environment (IDE) [3]

·         To learn VBA syntax, data types, flow of control, modularization [3]

·         To learn how to customize applications through programming [3]

·         To learn fundamentals of user interface design [2]

·         To learn the event model [2]

[Numbers in bracket’s indicate levels of knowledge on Bloom’s taxonomy]




Scale: A: 90-100; B: 80-89; C: 70-79; D: 60-69; F: <60. The grades of B+ and C+ may be given at the professor's discretion.

Final Grade Computation: Assignments 30%, Tests (2) 40%, Comprehensive Final Exam 20%, and Class Participation 10%.



·         You must do your assignments alone.  You are not allowed to discuss possible solutions with any person other than the instructor. You are not allowed to look at someone else’s solution (including code in books and the Internet) or show your solution to someone else other than the instructor.  See The Honor System of the College of Charleston and the Student Code of Conduct (, especially sections on Cheating, Plagiarism (pp. 10-11), and Computer Use (p. 13).

·         In-class activities, when identified as collaborative, are excluded from the above.

Course Policies:

·         Attendance at tests is mandatory.  You are expected to attend all classes.  Regardless of actual attendance, you are responsible for announcements made in class, assignment due dates, etc.

·         You are expected to do all reading assignments promptly.

·         Students are expected to participate in the educational experience through questions and invited comments/discussion.  However, you should respect your classmates right to learn (e.g., raise your hand, keep comments and discussions contained to the subject at hand, etc.); see Student Handbook section on Classroom Code of Conduct (pp. 49-50).

·         Programming assignments are to be submitted to the instructor on a floppy disk by the due date and time.  Clearly label your floppy disk with your name, course number, section number, and semester.  Make sure your floppy disk should be readable on MS Windows.

·         You have four “late” days for the whole semester to use when submitting your assignments.  Once you use up these days, no late assignments will be accepted. However, partial solutions submitted on time will be graded.

·         If at the end of the semester you still have all 4 “late” days unused and have completed all assignments, 2.5 bonus points will be added to your final course grade.