Thursday, October 18, 2007

Final Project Presentation

Presentation for the final project will be on October 19, Friday at Rm 308, DR2 and will start at 8:30AM.

Each group will be given 20 minutes starting with the first group from IT3A. The order of the presentation is arranged alphabetically based on the first member of the group as follows:

IT3A:
1. Alcoberes, et. al.
2. Arinto, et. al.
3. Barriga, et. al.
4. Basas, et. al.
5. Claro, et. al.
6. Gaanan, et. al.
7. Gio, et. al.

IT3B:
8. Abello, et. al.
9. Alay, et. al.
10. Albores, et. al.
11. Carado, et. al.
12. Co, et. al.
13. Deocampo, et. al.
14. Donayre, et. al.
15. Frigillano, et. al.
16. Masudo, et. al.
17. Polancos, et. al.

Wednesday, October 17, 2007

Using Crystal Reports

For those who are having problems with integrating Crystal Report in their applications, check this out:

http://www.crystalreportsbook.com/CrystalReportsXI.asp

Friday, October 12, 2007

Sample Codes: Data Access (2)

This sample improves the previous one by delegating all data access functions to a separate class named DBHelper. This also implements row filtering using the DefaultView property of a DataTable.

Download Code

This sample uses an MS Access database for persistent storage and adds reporting capabilities. This uses a different approach to retrieving and updating data by extending the DataSet class.

Download Code

To run both applications, set the ConnectionString value of the App.config file to the correct path of the databases. For the second example, Crystal Studio should be installed.

Thursday, September 20, 2007

Sample Code and Slide: Data Access

This sample uses the SQL provider to retrieve and manipulate data in an attached database (SQLExpress). This also demonstrates binding data to DataGridView and ComboBox controls.

To run the application, edit the AttachDbFilename value in the App.config file to point to the correct path of the database file. You can also copy the mdf/ldf files to a fixed location, e.g. "C:\", and set your AttachDbFilename value to "C:\Purchasing.mdf"

Download Code
Download Powerpoint Presentation

Wednesday, September 12, 2007

Final Program: Forms

Instruction: Submit this exercise on September 19, Wednesday. Compress the whole project located at "My Documents Path\Visual Studio 2005\Projects\Project Name" (default) or at the location you specified. Upload this file to ELMS. Also include the database design for your final project.

Continuing from exercise #8, create additional forms (a minimum of 3) for the transactions that your application will support. Each form should contain all fields necessary to process its corresponding transaction and should provide validation of its fields.

As an example, consider a Loans Management System which allows a group or a company to monitor all member loans. Possible transactions identified can include the following:
  • Loan Application - form to process member loan applications. Fields can include the transaction date, loan status, member information, loan type, loan cycle, loan amount, interest, mode of payment (monthly, weekly, etc) and terms of payment. Validation can be applied to numeric types like loan cycle, loan amount, and interest.
  • Loan Release - form to process loan disbursements. Fields can include the release date, loan status, and authorizing officer.
  • Loan Payment - form to process payments made by member. Fields can include the payment date, principal amount paid, interest amount paid, and cashier. Validation can be applied to numeric types.

Tuesday, August 28, 2007

Programming Exercise 8: Windows Forms 4

Instruction: Submit this exercise on September 10, Monday. Compress the whole project located at "My Documents Path\Visual Studio 2005\Projects\Project Name" (default) or at the location you specified. Upload this file to ELMS.

In preparation for your finals, you will be creating an application that will serve as the prototype for your final project. Although not fully functional, your application should implement these minimum requirements:
  • The application starts with a login form that will perform user validation. If the entered username and password are valid, load the main application form. If not, display an error. If the user clicks the Cancel button, the application should terminate. Since the application is not yet capable of storing data to a persistent storage, validate using "guest" as username and password for the meantime.
  • The application should also integrate your existing User Manager application. The User Manager form can be loaded when clicking the System -> Maintenance -> System Users menu item in the main application form.
  • The main application form should contain menu items similar to the sample given, i.e. it should have the following menus:
    • System - contains all menu items related to performing system functions
      • Maintenance - contains menu items related to configuring system-wide settings like system users and role assignments.
      • Masterfile - contains menu items related to configuring system-wide settings like lookup values used in transactions. An example of a menu item is "Loan Type" for a Loans Management System. Replace this with masterfiles related to your proposed system.
      • Exit - prompts a message confirming if the user wishes to close the application.
    • Transaction - contains all menu items related to performing system transactions. An example of a menu item is "Loan Application" for a Loans Management System. Replace this with transactions related to your proposed system.
    • Report - contains all menu items related to creating reports. An example of a menu item is "Loan Summary Report" for a Loans Management System. Replace this with reports related to your proposed system.
  • Create a System Configuration form similar to the sample given. This form does not need to implement any functionality yet and is reserved for future exercises.

The application should also integrate your existing User Manager application. The User Manager form can be loaded when clicking the System -> Maintenance -> System Users menu item in the main application form.
Hints: In addition to the existing controls you've used, this application also uses the following controls:
  • MenuStrip
  • StatusStrip
  • ListBox
  • TabControl
  • ComboBox
For the main application form, research on creating MDI forms.

You can download a sample output here.

Sample Code and Slide: Regular Expressions

This sample demonstrates using regular expressions for matching patterns in a string, which can be used to perform form data validation. This also uses a listbox form control for displaying results.

Download Code
Download Powerpoint Presentation