VB/C#

Need Help in Visual Basic and C# Assignments?
We can help you if you are having difficulty with your Visual Basic Assignment. Just email your assignments at support@assignmentcache.com.
We provide help for students all over the world.

Items 41 to 50 of 181 total

per page
Page:
  1. 3
  2. 4
  3. 5
  4. 6
  5. 7

Grid  List 

Set Ascending Direction
  1. CIS247A Week 7 Lab The Abstract RAcer Inheritance Hierarchy Program

    CIS247A Week 7 Lab The Abstract Racer Inheritance Hierarchy Program

    Regular Price: $15.00

    Special Price: $12.00

    CIS247A Week 7 Lab The Abstract Racer Inheritance Hierarchy Program


    Scenario and Summary
    This week, you will be implementing inheritance by creating a generic Racer base class along with two derived classes called StreetTuner and HotRod. You will make the Racer class abstract and include the abstract method IsDead() in the Racer class.


    STEP 1: Understand the UML Diagram
    The UML diagram four classes defined (1) Racer, (2) Engine, (3) Hot Rod, and (4) StreetTuner classes.


    The Racer class is the base parent abstract class of the Hot Rod and Street Tuner classes, which is represented by a directed line from the Hot Rod and Street Tuner classes to the Racer class and the end of the line touching the Racer class is a broad, unfilled arrow head. The racer class contains a engine object, which is represented by a directed line from the engine class to the Racer class, with a filled diamond touching the racer class, this line is labeled as a 1 to 1 relationship meaning that each racer object will contain one engine object and each engine is related to a single racer object.


    The class's attributes and methods are defined in separate class diagrams, and each class diagram is represented by a rectangular box subdivided into three vertically separated rectangular sub-sections. The top section contains the class name, the middle section contains the class attributes, and the bottom section contains the class methods.


    STEP 2: Build the Inheritance Hierarchy
    1. Create a project called "CIS247_WK7_Lab_LASTNAME".
    2. Build the class structure shown in the UML diagram. Remember to include properties for each class attribute.


    STEP 3: Implement the Logic for the HotRod Class
    1. Provide suitable logic for the ToString method. As always, the ToString method should reveal the state of an object.
    2. For the IsDead() method in HotRod, use the logic to implement the base class abstract IsDead method.
    Hint: To generate a random number, use the following code, which returns a random number from 0 to 1:
    Random rnd = new Random();
    rnd.NextDouble();

    Pseudocode for the IsDead method of HotRod
    Random rnd = new Random();
    boolean dead


    if (speed > 50 && rnd.NextDouble() > 0.6)
    if (engineHorsePower < 300 && blower=true)
    dead = false
    else
    dead = true
    end if
    else if (speed > 100 && rnd.NextDouble() > 0.4)
    if (engineHorsePower >= 300 && blower = true)
    dead = true
    else
    dead = false
    end if
    else
    dead = false
    end if


    STEP 4: Implement the logic for the StreetTurner class
    1. Provide suitable logic for the ToString method. As always, the ToString method should reveal the state of an object.
    2. For the IsDead method in StreetTurner, use the logic below to implement the inherited abstract base class method called IsDead.

    Pseudocode for the IsDead method of StreetTuner
    Random rnd = new Random();
    boolean dead
    if (speed > 50 && rnd.NextDouble() > 0.6)
    if (engineHorsePower < 300 && nitrous=true)
    dead = false
    else
    dead = true
    end if
    else if (speed > 100 && rnd.NextDouble() > 0.4)
    if (engineHorsePower >= 300 && nitrous = true)
    dead = true
    else
    dead = false
    end if
    else
    dead = false
    end if


    STEP5: Construct the Main Program
    1. Create an array of Racer objects that will hold two Racer objects.
    2. Write a method called CollectRacerInformation that accepts as an argument a Racer object, and then prompts the user to provide the following information for each racer:
    a. Racer name;
    b. Racer Speed;
    c. Number of cylinders in the racer's engine;
    d. Horsepower of the racer's engine; and
    e. Nitrus or blower option, depending on the type of Racer object.
    [Hint: In order to be able to collect all information for the derived classes as well, consider creating a base class method called ReadRacerData in the Racer class, which you will then override in the derived classes to capture the required info per class. Call the ReadRacerData method within the CollectRacerInformation method.]
    3. Write a method called "DisplayRacerInformation" that accepts as an argument a Racer object, and then displays all of the information for the specific racer type.
    4. Create a racer object of each type, and invoke the CollectRacerInformation passing in the Racer object. Then, store each object in the array.
    5. Iterate through the Racer array list and, for each Racer, display all of the Racer's attribute information (call the DisplayRacerInformation method for each object). Don’t forget to indicate whether or not the Racer is dead!


    STEP 6: Compile and Test
    When done, compile and run your program.
    Then, debug any errors until your code is error-free.
    Check your output to ensure that you have the desired output and modify your code as necessary and rebuild. Your code may resemble the following:

    Welcome the Abstract RAcer Inheritance Hierarchy Program
    CIS247, Week 7 Lab
    Name: Solution
    This Program test an Anstract Racer Inheritance hierarchy
    **************** Collecting Racer's Basic Data ****************
    Enter racer's name: Fast One
    Enter racer's speed: 345
    Enter number of cylinders in racer's engine: 20
    Enter horsepower of racer's engine: 250
    Enter nitrus option (Y/N): Y
    **************** Collecting Racer's Basic Data ****************
    Enter racer's name: Lightning
    Enter racer's speed: 380
    Enter number of cylinders in racer's engine: 16
    Enter horsepower or racer's engine: 275
    Enter blower option (Y/N): Y
    **************** Display Racer's Data ****************
    Racer's Name : Fast One
    Racer's Speed : 345
    Engine Cylinders : 20
    Engine Horsepower : 250
    Racer's Type : STREET TUNER
    With Nitrus Option : Yes
    Still Working? : Yes!
    **************** Display Racer's Data ****************
    Racer's Name : Lightning
    Racer's Speed : 380
    Engine Cylinders : 16
    Engine Horsepower : 275
    Racer's Type : HOT ROD
    With Nitrus Option : Yes
    Still Working? : Yes!
    Thank you for using the Abstract Racer Inheritance Hierarchy

    Learn More
  2. Programming In VB Multiform Projects 6.4 Taste Tester

    Programming In VB Multiform Projects 6.4 Taste Tester

    Regular Price: $20.00

    Special Price: $15.00

    Programming In VB Multiform Projects 6.4 Taste Tester


    A battle is raging over the comparative taste of Prune Punch and Apple Ade. Each taste tester rates the two drinks on a scale of 1 to 10 (10 being best). The proof of the superiority of one over the other will be tl1e average score for the two drinks.


    Display a splash screen and then the main form. The main form has only the menus: you can add a graphic if you wish.


    Main Form Menu
    File Help
    New Tester About
    Summary
    Exit


    New Tester Menu Item
    The New Tester menu item displays a form that inputs the test results for each drink. The form contains an OK button and a Close button. When the user clicks the OK button. add the score for each type of drink to the drink's total. clear the text boxes. and reset the focus. Leave the form on the screen in case the next tester is ready to enter scores. If enter score is blank when the OK button is pressed. display a message in a message box and reset the focus to tile box for the missing data.
    The Close button returns to the main form without performing any calculation.


    Summary Menu Item
    The Summary item displays a form that contains the current results of the taste test. It should display the winner. the total number of taste testers, and the average rating for each drink. The form contains an OK button that returns to the main form. (The user will be able to display the summary at any time and as often as desired.)


    About Box
    The About box should display information about the program and the programmer.
    Include an OK button that returns the user to the main form.

    Learn More
  3. BMIS 208 Programming Assignment 3 Analyze Mortgage

    BMIS 208 Programming Assignment 3 Analyze Mortgage

    Regular Price: $15.00

    Special Price: $12.00

    BMIS 208 Programming Assignment 3 Analyze Mortgage


    Adapted from Introduction to Programming Using Visual Basic 2012, 9/E, David I. Schneider


    Create a Visual Basic program to analyze a mortgage. The user should enter the amount of the loan, the annual percentage rate of interest, and the duration of the loan in months. When the user clicks on the button, the information that was entered should be checked to make sure it is reasonable. If bad data have been supplied, the user should be so advised. Otherwise, the monthly payment and the total amount of interest paid should be displayed. The formula for the monthly payment is:
    Payment = p * r / (1 – (1 + r) ^ (-n)),
    Where p is the amount of the loan, r is the monthly interest rate (annual rate divided by 12) given as a number between 0 ( for 0 percent) and 1 (for 100 percent), and n is the duration of the loan in months.The formula for the total interest paid is:
    total interest = n * payment – p.
    1. Design your screen to look like the one below.
    2. Store the amounts entered by the user in variables and use these variables in the formula.
    3. Use appropriate naming conventions for controls and variables.
    4. Include internal documentation to describe the logic in your program (i.e. put comments in your code).
    5. Make sure your error messages are meaningful.
    6. Ensure that the user cannot enter anything into controls that display your totals.

    Learn More
  4. Programming In VB List, Loop and Printing Exercise 7.4 Search US States

    Programming In VB List, Loop and Printing Exercise 7.4 Search US States

    Regular Price: $15.00

    Special Price: $12.00

    Programming In VB List, Loop and Printing Exercise 7.4 Search US States


    7.4 Create a project that contains a list box with the names of all U.S. states and territories. When the user types the first letters of the state into a text box. set the Selected Index property of the list box to display the appropriate name. Include an Exit menu item.


    Alabama Kentucky Oklahoma
    Alaska Louisiana Oregon
    American Samoa Maine Pennsylvania
    Arizona Maryland Puerto Rico
    Arkansas Massachusetts Rhode Island
    California Michigan South Carolina
    Colorado Minnesota South Dakota
    Connecticut Mississippi Tennessee
    Delaware Missouri Texas
    District or Columbia Montana Trust Territories
    Florida Nebraska Utah
    Georgia Nevada Vermont
    Guam New Hampshire Virgin Island.
    Hawaii New Jersey Virginia
    Idaho New Mexico Washington
    Illinois New York West Virginia
    Indiana North Carolina Wisconsin
    Iowa North Dakota Wyoming
    Kansas Ohio

    Learn More
  5. CIS407 Lab 1 Week 1 Annual Salary Calculator ASP.NET Web Application

    CIS407 Lab 1 Week 1 Annual Salary Calculator ASP.NET Web Application

    Regular Price: $10.00

    Special Price: $8.00

    This course has expired to download the latest version of CIS407A Labs click here


    CIS 407 iLab 1 of 7: "Annual Salary Calculator" ASP.NET Web Application


    iLAB OVERVIEW
    Scenario/Summary
    In this iLab, you will create an Annual Salary Calculator ASP.NET web application using Visual Studio.NET 2008.
    For the iLabs, you will use the Microsoft Visual Studio 2008 software application. You have two options for using this application:
    • You may use a copy of Visual Studio 2008 that is installed on your local PC. If you do not already have this software, there is a link in the Syllabus (in the Textbook and Required Materials section) that you can follow to obtain a copy at low or no cost through the DeVry Student Software Fulfillment Center.
    or
    • You may run Visual Studio 2008 over the Web from the DeVry iLab (Citrix) server. Instructions for using the iLab (Citrix) server are on the iLab page under Course Home.
    Throughout this course, you will be creating a web application for a fictitious company called CoolBiz Productions, Inc. To get familiar with the development environment, follow the Lab Steps to create a simpleAnnual Salary Calculator ASP.NET web application. You will be adding to this application each week.
    Instructions for Week 1 iLab: "Hello World, and more" ASP.NET Web Application
    Click on the link above to view the tutorial.
    Please watch this tutorial before beginning the iLab.
    The tutorial has audio.


    Overview of Fictitious Company
    CoolBiz Productions, Inc.
    We are a mid-size indie (independent) film studio that is in need of a payroll system. We have outgrown our current system, a simple spreadsheet, to the extent that it takes three people over one week to pay everyone on a timely basis.
    Overview of Our Company
    We have over 2,000 full-time and part-time employees. We produce comedy, fiction, and science fiction films with budgets of $250K–$20 million. We have produced over 50 films since we first began 20 years ago.
    We are very profitable and have strong links to many of the industry's most powerful people.
    Current Payroll System
    Our current system consists of mostly manual processing using an MS Excel spreadsheet to control who gets paid.
    The system consists of the three payroll staff members reviewing each of the full-time staff members' wages, calculating how many hours they worked based on their hourly rate, and paying them by issuing a check.
    The check needs to be entered in another worksheet for each of the people who were paid so that we can tell when it went out, how much it was for, and if it was cashed or not. If a [Date_Cashed] is entered, we deduct that amount from our working payroll capital account to track how much money we have for payroll.
    This process is then repeated for all part-time staff and independent contractors.
    Our Needs
    We need a more automated way to pay our staff. We need to use the same logical flow as a basis, yet improve on it by having a way to
    1. easily calculate the projected annual salary based on rate and number of hours;
    2. search, enter, update, and delete staff and independent employee information in one place;
    3. search, enter, update, and delete payroll automation information for the employee to set up recurring payments or one-time payments;
    4. produce reports to show the following: (a) summary of who got paid per week, (b) summary of all payments per week, (c) details of any employee to-date (allow entry of a specific employee ID);
    5. allow transactions to be rolled back in case we pay someone too much;
    6. make use of transaction processing in case the system unexpectedly shuts down;
    7. ensure the system is secure (logins required);
    8. allow only authorized payroll personnel to control all aspects of the system;
    9. allow only authorized payroll personnel to view transactions and user activity;
    10. allow only authorized payroll personnel to e-mail reports to users using the e-mail on file; and
    11. incorporate error handling into all processes in the system and e-mail any errors to the technical support people.


    Deliverables
    All files are located in the subdirectory of the website. The website should function as follows: You should have a page that, when run, displays a page showing the text "Hello, World." You should also have a second page that is the annual salary calculator that properly calculates the annual salary, given an hourly rate and the number of hours projected to be worked in a year. Once you have verified both pages work, save your website, zip up all files, and submit in the Dropbox.


    iLAB STEPS
    STEPS 1 through 3: Create Website and Home Page (10 points)
    In this ilab, we will learn how to create a simple ASP.NET web application using Microsoft Visual Studio.NET 2008. The application will display the text "Hello, World" on the home page.
    1. Open Microsoft Visual Studio 2008.
    2. Create a new ASP.NET website called "PayrollSystem." To do this, select "File, New Website."
    When the "New Website" dialog opens, select "ASP.NET Website" as the Template, select "File System" as the Location, and select "Visual C#" as the Language. Click Browse and navigate to the folder where you want to save your website. Add "PayrollSystem" at the end of the file path. Click OK if you are prompted to create a new folder. Click OK in the New Website dialog to finish creating the website.
    3. Edit the Default.aspx file (the home page for your site) to add the message "Hello, World." To do this, if necessary, click the Design button below the editing window to switch to Design view, then click in the editing window and type "Hello, World" (without the quotes).
    Click the Save button on the toolbar to save the changes to Default.aspx.

    STEPS 4 through 5: Start Debugging (10 points); NOTE: Citrix users have different steps!
    4. To ensure that everything is working properly, click the Start Debugging button on the toolbar, or press the F5 key on the keyboard, or pull down the Debug menu and select "Start Debugging."
    5. If the "Debugging Not Enabled" dialog box appears, select the option to add or modify the Web.config file to enable debugging and click OK. You should only have to do this the first time you debug the site.
    NOTE: To execute the application, you have these options:
    A. If you are using Citrix, press CTRL + F5 to Start Without Debugging. You will not be deducted points for this part.
    B. If you are using a standalone version, press F5 to Start with Debugging, or you can press CTRL + F5 to Start Without Debugging


    STEP 6 through 7 : Display the "Hello, World" web page (10 points)
    6. The Internet Explorer web browser will open and display your Default.aspx page containing the "Hello, World" message.
    7. Click here for text description of this image.
    8. Stop debugging and return to the design mode by closing the browser.
    9. Add a new form to your web application called frmSalaryCalculator.aspx. Make sure "Place Code in separate file" is checked when you add the form. To add a new form, click (single-click, not double-click) on the project node in the solution explorer.
    With the project node highlighted, right-click on the project node and select "Add New Item" from the popup menu. The following dialog will be displayed:
    Select the name of the form you will add frmSalaryCalculator.aspx. Make sure "Place code in separate file" is checked and "Select master page" is unchecked.
    10. You will create a web-based salary calculator on this new page. To do this, open the aspx page in Design view and, from the Toolbox, add three labels, two text box controls, and a button control. You can add controls by dragging the control from the Toolbox – Standard section onto your form. Your form should look like this:
    11. Change the text displayed in each label so that the first label displays "Annual Hours"; the second label should display "Rate" and the third label should display "$". (Hint: To change the text displayed, change the Text property of each control.)
    12. Change the button text to display "Calculate Salary." (Hint: To change the text displayed as the button label, change the Text property of the button.) Your form should now look like this:
    13. Set the ID property of the top text box to txtAnnualHours. Set the ID property of the second textbox to txtRate. Set the ID of the bottom label (the one we set the text property to "$") to lblSalary. (Note: We set these IDs as we will be accessing the control values from the C# code. You can set the button ID and the other two labels' ID properties as well, but we won't be accessing them from our code.)
    14. In Design view, add a C# event handler for the button-click event by double-clicking on the Calculate Salary button. This will place you in the page code behind file the editor. (Remember that ASP.Net pages have a file containing the HTML markup with an extension of .aspx and a C# 'code behind' file with an extension of .aspx.cs.) This is the code that should be displayed: (If you changed the ID of the button, it will be a different method name.)
    This code will be called each time the user presses the button. It is important to remember that code in the code behind page executes on the server – not on the user's browser. This means that when the button is pressed, the page is submitted back to the web server and is processed by the ASP.Net application server on the web server. It is this code (between the { and } in this method) that will execute on the server. Once it is done executing the page will be sent back to the browser. Any changes we make to the page or controls on the page will be shown to the user in the updated page.
    15. In this method, add code that will get the text in the txtAnnualHours text box, convert it to a Double, and store it in a double variable. Add code that will get the text from the txtRate text box, convert it to a Double, and store it in another variable. Create a third variable of type Double and set its value to the annual hours variable value multiplied by the rate double variable value. Take this resulting value and convert it to a string (text), and update the lblSalary Text property with this new string.
    Hints: A control's property can be accessed by simply using the control ID followed by a . followed by the name of the property. For example, the value stored in the Text property of the txtAnnualHours control can be accessed by using this: txtAnnualHours.Text. Text properties on controls are of type string.
    To convert a string to a Double you can use the Convert class. If we had a string variable called str1 and a double variable called myNumber, the C# code to convert this would be as follows:
    When converting from one type to another, we are assuming that the value stored in the type being converted is compatible with the type we are converting to. In the example above, if the value stored in str1 was not type compatible with a Double (for example "tiger") an error would be raised.
    To set the value of a control on a web form, you can access the control and set the property directly. If I had a label control called lblCar and I wanted to update the text that was displayed in the label, I could do something like this:
    Note that following code would be incorrect and cause an error:
    lblCar is a Label – it isn't a string so we can't assign a string directly to it, but we can assign a string directly to the Text property of the label.
    All of the base types in C# (double, int etc) have a ToString() method you can call. If you had a double variable that you wanted to convert to a string and set that string to my label's text, you would do the following:
    This would take whatever value was stored in the myNumber Double and convert it to a string.
    To add a $ to output you can use string concatenation in C# like this:
    16. Set your new form as the start page by clicking once on the form name in the Solution Explorer and then right-clicking on the form name and selecting "Set as Start Page." You can now test your application and make sure it works correctly as you did with the Hello World form above. You can switch back and forth between which form runs when you run your application by setting the different forms as the start page.
    Once you have verified that your project works, save your project, zip all files, and submit in the Dropbox.
    NOTE: Please download and review the Doc Sharing files Web Lab and Citrix.zip, which contain information on how to FTP to the DeVry University website and how to use Citrix for the assignments.

    Learn More
  6. CIS407 Lab 2 Week 2 frmMain Web Form

    CIS407 Lab 2 Week 2 User Input Web Pages ASP.NET Web Application

    Regular Price: $12.00

    Special Price: $10.00

    This course has expired to download the latest version of CIS407A Labs click here


    CIS 407 iLab 2 of 7: User Input Web Pages


    iLAB OVERVIEW
    Scenario/Summary
    In this lab, we will demonstrate how to create an ASP.NET web application having a single form with five text boxes and a Submit button. We will use the form to send information to a second form where data from the first form will be displayed. We will also add a main navigation page with two different ways of linking to other pages. INCLUDE A SCREENSHOT OF THE ASSIGNMENT SUCCESSFULLY RUNNING TO RECEIVE CREDIT


    Deliverables
    All files are located in the subdirectory of the website. The website should function as follows: When you run the website, you will be presented with a page (frmMain) that allows you to go to the different parts of the website you are developing. You will be able to go to the annual salary calculator we added last week and to the data entry form for personnel this week. When you go to the personnel data entry page you should be able to enter data in the frmPersonnel form and have it displayed in the frmPersonnelVerified form. Your salary calculator will also be available from the main page and will calculate properly when you enter data. Each page should link back to the main page via the CoolBiz logo hyperlink. Once you have verified it works, save your website, zip up all files, and submit in the Dropbox. Each page (except frmMain) will include the CoolBiz logo that is hyperlinked back to frmMain.


    iLAB STEPS
    STEP 1: frmPersonnel (10 points)
    1. Open the payroll system website from Lab 1.
    2. Create a new form called frmPersonnel. To do this, pull down the website menu, select "Add New Item," then type frmPersonnel.aspx for the name.
    3. Click here for text description of this image.
    4. Go to the Design mode of the form by clicking the Design tab (as opposed to the Source tab).
    5. Copy/paste this text for the CoolBiz Productions, Inc. logo onto the form at the very top. Set the alignment to center by highlighting the text then clicking Format, Justify, Center. You can switch to Source view and add the following HTML to create the logo:
    <font color="black" size="2"><strong><fontcolor="blue" face="Comic Sans MS"size="4">Cool</font><font color="#ff6600"face="Comic Sans MS" size="4">Biz</font><font face="Comic Sans MS" size="4"> <fontcolor="#993366">Productions</font>, Inc.</font></strong> </font>
    6. From the ToolBox, drag-and-drop a Panel control underneath the logo text.
    7. Click the A/Z button in the Properties dialog so that all the properties are sorted alphabetically.
    8. Change the height property of the Panel to 250px and the width to 300px. To do this, select the Panel, then go to the Properties pane (usually in the lower right corner of the Visual Studio.NET Design view; if you don't see it, click View Properties Window OR press the F4 key). Scroll down the list, then type the value in for each property.
    9. Change the panel's HorizontalAlign property to left.
    10. Save your work!
    11. From the ToolBox, drag-and-drop five Labels and five TextBoxes onto the Panel. To make each Label/TextBox pair appear on a separate line, put the cursor after each TextBox then press the [ENTER] key (much like you would with a word processing program).
    12. From the ToolBox, drag-and-drop two buttons onto the Panel below the last Label and TextBox.
    13. Save your work! INCLUDE A SCREENSHOT OF THE ASSIGNMENT SUCCESSFULLY RUNNING TO RECEIVE CREDIT
    14. Click here for text description of this image.
    15. Test your web page. Press F5, or click the Start Debugging (Citrix users, press "Start Without Debugging") button on the toolbar, or pull down the Debug menu and select Start Debugging.
    NOTE: To execute the application, you have these options:
    A. If you are using Citrix, press CTRL + F5 to Start Without Debugging. You will not be deducted points for this part.
    B. If you are using a standalone version, press F5 to Start with Debugging, or you can press CTRL + F5 to Start Without Debugging
    16. Rename the Label's properties as defined below. You can do this by selecting each Label, scrolling to the property, and then typing in the value.
    Property Value
    Label1 – Text First Name:
    Label2 – Text Last Name:
    Label3 – Text Pay Rate:
    Label4 – Text Start Date:
    Label5 – Text End Date:
    17. Rename each TextBox's property as defined below. You can do this by selecting each TextBox, scrolling to the property, and then typing in the value.
    Property Value
    TextBox1 – (ID) txtFirstName
    TextBox2 – (ID) txtLastName
    TextBox3 – (ID) txtPayRate
    TextBox4 – (ID) txtStartDate
    TextBox5 – (ID) txtEndDate
    18. Click on image to enlarge.
    Changing Text Box ID
    19. Click here for text description of this image.
    20. Change each button's ID and Text properties as defined below. You can do this by selecting each button, scrolling to the property, and then typing in the value.
    Property Value
    Button1 – (ID) btnSubmit
    Button1 – Text Submit
    Button2 – (ID) btnCancel
    Button2 – Text Cancel
    21. In order to format the TextBoxes and Labels, we will make them the same size. Bring up the Layout Toolbar by clicking View, Toolbars, Layout.
    22. Highlight each Label by pressing and holding the keyboard Ctrl button and then clicking each Label. Make sure you click on the longest Label last.
    23. Click the icon "Make Same Width" on the Layout Toolbar. (You may also select Format and then Make Same Size and then select width).
    24. Save your work!
    25. Test your work by running it (press F5 or click the Start Debugging button, or click Debug, Start Debugging).


    STEP 2: frmPersonalVerified (5 points)
    22. Create a new web form called frmPersonalVerified.aspx
    23. Click the Design tab for the frmPersonalVerified.aspx and add a Label and a TextBox. Set the properties as follows:
    Property Value
    Label – Text Information to submit
    Textbox – (ID) txtVerifiedInfo
    Textbox – Height 80px
    Textbox – Width 400px
    Textbox – TextMode Multiline
    24. Double-click anywhere on a blank part of the web page to open the code portion. The cursor should be in the protected void Page_Load (object sender, EventArgs) function. Enter the following information:
    //Add your comments here
    txtVerifiedInfo.Text = Request["txtFirstName"] +
    "\n" + Request["txtLastName"] +
    "\n" + Request["txtPayRate"] +
    "\n" + Request["txtStartDate"] +
    "\n" + Request["txtEndDate"];
    25. Return to the frmPersonnel web page, click the btnSubmit button, go to the PostBackUrl property, and set it to frmPersonalVerified.aspx. To do this, you can click the ellipse to the right of this property to open a Browse dialog and click frmPersonalVerified.aspx there. This will insert the correct path into the PostBackUrl property.


    STEP 3: Adding Navigation (5 points)
    26. Create a folder in Solution Explorer called images.
    27. Add a new web form called frmMain.
    A. Add the CoolBiz Logo to the top of the form (centered).
    B. Create links using a link button for each of the following items.
    Salary Calculator
    Add New Employee
    C. Create or find appropriate images for the Salary Calculator and New Employee links. Copy the images to the images folder created above.
    D. Add the images to the images folder by right-clicking on the images folder in Solution Explorer and selecting Add Existing Items. Select both images and Add to the images folder.
    E. Next to each link item, add an image button.
    F. Set each image button's image to the appropriate image in the images folder.
    G. You may work with the format to make this page look nice by using tables or other HTML/CSS elements.
    H. Set the PostbackURL property to the appropriate page for each image and each link.
    28. On the frmPersonnel page, make the CoolBiz logo be a link that will take the user to the frmMain page. Use an ASP.Net Hyperlink control to do this.
    29. Update the frmPersonnel, frmPersonnelVerified, and frmSalaryCalculator to include the CoolBiz logo at the top of each page (centered) with the logo set as a hyperlink that will return to the frmMain page.
    30. On the frmPersonnel page, make it so that if the user presses the Cancel button then that user is taken back to the frmMain.


    STEP 4: Verify and Submit (10 points)
    31. Save your work. Set the start page to frmMain and run the project. You should be able to go to both areas of your site and enter the information in the pages. Your calculator should properly calculate without errors, and then on the frmPersonel web page you can click the Submit button and have it display in the frmPersonalVerified web page. Once you have verified that it works, save your project, zip up all files, and submit in the Dropbox.
    Here are screen shots (Note: Your frmMain does not have to look exactly like this, as long as it functions.):
    frmMain:
    frmSalaryCalculator:
    frmPersonnel:
    frmPersonnelVerified:
    All Forms:


    NOTE: Make sure you include comments in the C# code where specified (where the "//Your comments here" is mentioned), or else a 5 point deduction per item (form, class, function) will be made. This includes code you will be creating in the coming weeks. To comment on the code you basically put two forward slashes to start the comment; anything after the slashes on that line is disregarded by the compiler. Then type a brief statement on what is happening in the line under it. Comments show professionalism and are a must in systems. As a professional developer, comments will set you apart from others and make your life much easier if maintenance and debugging are needed.

    Learn More
  7. CIS407 Lab 3 Week 3 frmMain Web Form

    CIS407 Lab 3 Week 3 User activity monitoring ASP.NET Web Application

    Regular Price: $12.00

    Special Price: $10.00

    This course has expired to download the latest version of CIS407A Labs click here


    CIS 407 iLab 3 of 7: User activity monitoring


    iLAB OVERVIEW
    Scenario/Summary
    In this lab, we will demonstrate how to save user activity data in a database. We will be creating a new form to display the user activity data, a new dataset to contain the data, a data access class to structure the code, and a function within the data access class to save users' activity data when users visit the Personnel form page (frmPersonnel.aspx). We will also be adding server side validation to the frmPersonnel for you added in the previous lab and update or main menu for the new functionality. INCLUDE A SCREENSHOT OF THE ASSIGNMENT SUCCESSFULLY RUNNING TO RECEIVE CREDIT


    Deliverables
    All files are located in the subdirectory of the project. The project should function as specified: When you visit the Personnel form page (frmPersonnel.aspx), a record should be saved in the tblUserActivity table with the IP address, form name accessed (frmPersonnel), and the date accessed. When you click the "View Activity" button, you should see at least one record with this information. When the user goes to the frmPersonnel web form and enters data the following business rules are to be enforced:
    • Fields may not be empty or filled with spaces. If any field is empty, turn that field background color to yellow and add to/create an error message to be shown in the error label.
    • The end date must be greater than the start date. If the end date is less than the start date turn both date fields yellow and add to/create an error message to be shown in the error label.
    If all fields validate properly, then the session state items should be set properly and the user should see the frmPersonnelVerified form with all the values displayed. You will also add a new item to frmMain that will take the user to the new frmUserActivity form you added. Add the proper link and a hyperlinked image to allow the user to select this new option. Once you have verified that everything works, save your website, zip up all files, and submit in the Dropbox.


    iLAB STEPS
    STEP 1: Data Connection, Dataset and Data Access Class (10 points)
    1. Open Microsoft Visual Studio.NET 2008.
    2. Open the PayrollSystem website by clicking on it in the Recent Projects list, or by pulling down the File menu, selecting Open Website, navigating to the folder where you previously saved the PayrollSystem, and clicking Open.
    3. Download the PayrollSystem_DB.MDB file from Doc Sharing and save it on your local computer. (Note: your operating system may lock or block the file. Once you have copied it locally, right click on the file and select Properties and then Unblock if available). Then add it to the PayrollSystem website as follows: In Visual Studio, in the Solution Explorer click Website, Add Existing Item, then navigate to the PayrollSystem_DB.MDB file you downloaded and click the Add button.
    4. Now we need to create a new connection to the PayrollSystem_DB.MDB. To begin, click View Server Explorer.
    5. When the Server Explorer toolbox appears, click the Connect to Database button.
    6.When the Add Connection dialog appears, click the Change button. In the "Change Data Source" dialog, select MS Access Database File; Uncheck Always use this Selection; then click OK.
    7. Click the Browse button to navigate to the PayrollSystem_DB.mdb file in your website folder, then click "Open". (NOTE: Be sure you select the PayrollSystem_DB.mdb file in your PayrollSystem website folder, not the one you originally downloaded from Doc Sharing!) Click Test Connection. You should receive a message that the test connection succeeded. Click OK to acknowledge the message, then click "OK" again to close the Add Connection dialog.
    8. The PayrollSystem_DB.mdb should be added to the Server Explorer. Expand the database, then expand the Tables entry under the database until you see tblUserActivity. Leave the Server Explorer window open for now as you will be returning to it in a moment.
    9. Create a new dataset by selecting Website Add New Item. Under Templates, select the Dataset item. Enter dsUserActivity.xsd for the name. Click Add.
    10. Click here for text discription of this image.
    11. If the following message appears, select Yes. You want to make this dataset available to your entire website.
    12. If the TableAdapter Configuration Wizard dialog appears, click Cancel. (We will be configuring a Data Adapter for this dataset later in C# code, so we do not need to run this wizard.)
    13. Drag-and-drop the tblUserActivity table from the Server Explorer window into the dsUserActivity dataset in the editor window.
    NOTE: If you see a message that says your connection uses a local data file that is not in the current project, that indicates you did not select the correct PayrollSystem_DB.mdb file when you created your data connection. To fix this problem, click No, then right-click on PayrollSystem_DB.mdb in the Server Explorer window and choose Modify Connection. Click the Browse button, navigate to the PayrollSystem_DB.mdb file that is in your PayrollSystem website folder, and click Open. Test the connection, then click OK.
    14. Click the Save icon on the toolbar to save the dsUserActivity.xsd dataset.
    15. Click here for text discription of this image.
    16. (You can now close the Server Explorer window if you wish.)
    17. Create a new class to contain the C# code that will access this dataset. To do so, click Website, Add New Item. In the Add New Item dialog, select the Class template, and enter clsDataLayer for the name. Make sure the Language is set to Visual C#. Click "Add".
    18. Click here for text discription of this image.
    19. If the following message appears, select Yes. You want to make this class available to everything in your solution.
    20. Add the following to the top of your class, below any other using statements created for you by Visual Studio:
    // Add your comments here
    using System.Data.OleDb;
    using System.Net;
    using System.Data;
    21. Add the following three functions inside the squiggly braces for the "public class clsDataLayer" class, above the beginning of the "public clsDataLayer()" constructor:
    // This function gets the user activity from the tblUserActivity
    public static dsUserActivity GetUserActivity(string Database)
    {
    // Add your comments here
    dsUserActivity DS;
    OleDbConnection sqlConn;
    OleDbDataAdapter sqlDA;
    // Add your comments here
    sqlConn = new OleDbConnection("PROVIDER=Microsoft.Jet.OLEDB.4.0;" +
    "Data Source=" + Database);
    // Add your comments here
    sqlDA = new OleDbDataAdapter("select * from tblUserActivity", sqlConn);
    // Add your comments here
    DS = new dsUserActivity();
    // Add your comments here
    sqlDA.Fill(DS.tblUserActivity);
    // Add your comments here
    return DS;
    }
    // This function saves the user activity
    public static void SaveUserActivity(string Database, string FormAccessed)
    {
    // Add your comments here
    OleDbConnection conn = new OleDbConnection("PROVIDER=Microsoft.Jet.OLEDB.4.0;" +
    "Data Source=" + Database);
    conn.Open();
    OleDbCommand command = conn.CreateCommand();
    string strSQL;
    strSQL = "Insert into tblUserActivity (UserIP, FormAccessed) values ('" +
    GetIP4Address() + "', '" + FormAccessed + "')";
    command.CommandType = CommandType.Text;
    command.CommandText = strSQL;
    command.ExecuteNonQuery();
    conn.Close();
    }
    // This function gets the IP Address
    public static string GetIP4Address()
    {
    string IP4Address = string.Empty ;
    foreach (IPAddress IPA in
    Dns.GetHostAddresses(HttpContext.Current.Request.UserHostAddress)) {
    if (IPA.AddressFamily.ToString() == "InterNetwork") {
    IP4Address = IPA.ToString();
    break;
    }
    }
    if (IP4Address != string.Empty) {
    return IP4Address;
    }
    foreach (IPAddress IPA in Dns.GetHostAddresses(Dns.GetHostName())) {
    if (IPA.AddressFamily.ToString() == "InterNetwork") {
    IP4Address = IPA.ToString();
    break;
    }
    }
    return IP4Address;
    }


    STEP 2: frmUserActivity, frmPersonnel, frmMain (10 points)
    18. Create a new Web form called frmUserActivity. Switch to Design Mode and add a Label and GridView (found under the Toolbox, Data tab) having the following properties:
    Property Value
    Label - Text User Activity
    GridView - (ID) grdUserActivity
    19. Go to the Page_Load method and add the following code:
    if (!Page.IsPostBack) {
    // Declares the DataSet
    dsUserActivity myDataSet = new dsUserActivity();
    // Fill the dataset with what is returned from the function
    myDataSet = clsDataLayer.GetUserActivity(Server.MapPath("PayrollSystem_DB.mdb"));
    // Sets the DataGrid to the DataSource based on the table
    grdUserActivity.DataSource = myDataSet.Tables["tblUserActivity"];
    // Binds the DataGrid
    grdUserActivity.DataBind();
    }
    20. Open the frmMain form, add a new link button and image button to point to the new frmUserActivity. Find an image to use for the image button and add the new option as View User Activity.
    21. Go to the frmMain Page_Load and add the following code:
    // Add your comments here
    clsDataLayer.SaveUserActivity(Server.MapPath("PayrollSystem_DB.mdb"), "frmPersonnel");
    22. On the frmUserActivity form, add the CoolBiz logo hyperlinked logo at the top of the page so that when clicked the user is returned to frmMain.
    23. In the Solution Explorer, right click on the frmMain.aspx form and select Set As Start Page. Run your project. When you open the project, a record should be saved in the tblUserActivity table with the IP address, form name accessed (frmPersonnel), and the date accessed. When you click the View Activity button, you should see at least one record with this information.
    24. You will now add server side validation code to the frmPersonnel page. Currently, when the Submit button is pressed, the frmPersonnelVerified page is displayed. This is because the frmPersonnelVerified page is set as the Submit button's PostBackUrl property. Instead of having the page go directly to the frmPersonnelVerified page when the Submit button is pressed, we want to do some server side validation. If any of the validation rules fail, we will redisplay the frmPersonnel page with the fields in question highlighted in yellow with an error message displayed.
    First, it is important to understand what is currently happening when the submit button is pressed. This is causing a postback of the form to the frmPersonnelVerified form. When this postback happens, all of the data in the fields on the frmPersonnel form are sent to the frmPersonnelVerified form as name value pairs. In the Page_Load code of frmPersonnelVerified these values are picked up from the Request object and displayed. Each name value pair will be in the Request object as the ID of the control containing the value and the value itself. We can pass data between pages by using Session state instead. In order to do validation on the values but still have the values visible on the frmPersonnelVerified page, we will need to change not only the PostBack URL of the frmPersonnel page but also how the frmPersonnelVerified form is getting the data – it will need to get it from Session state rather than from the Request object.
    Make the following changes:
    1. Clear the Submit button PostBackURLProperty on the frmPersonnel form.
    2. In the btnSubmit_Click event handler get each value from the data entry fields and set Session state items for each.
    3. Change the frmPersonnelVerified code behind to get the values from the Session state items you created in the previous step.
    When you are done with these steps, you should be able to enter data on the frmPersonnel data entry form and then click the Submit button. The frmPersonnelVerified page should then be displayed with the values that were in the data entry fields on frmPersonnel.
    Make sure this is all working before proceeding to the next steps.
    25. Add a label to the frmPersonnel form with an ID of lblError. Do not place the label to the right or left of any of the controls on the form. Add it below the controls or above the controls. The text property of this label should be set to an empty string.
    26. Add code to perform server side validation in response to the submit button being clicked. Here are the business rules we want to enforce (remember this will be server C# code in the frmPersonnel code behind): Fields may not be empty or filled with spaces. If any field is empty, turn that field background color to yellow and add to/create an error message to be shown in the error label. The end date must be greater than the start date. If the end date is less than the start date, turn both date fields yellow and add to/create an error message to be shown in the error label. If all fields validate properly then the session state items should be set properly and the user should see the frmPersonnelVerified form with all the values displayed.
    27. Lab Hints: To set a value in session state do the following:
    Session["txtFirstName"] = txtFirstName.Text;
    28. "txtFirstName" is the key and txtFirstName.Text is the value.
    29. To get this same value back from the session we use the key and the Session object as follows:
    Session["txtLastName"].ToString()
    30. There is a Trim method on the string object that will automatically remove spaces from the beginning and end of a string. Remember, you can turn an object like a Session item object into a string using the Convert class or just using it's ToString() method.
    31. You may want to create variables to work with for validation rather than using the Request item objects directly.
    32. To turn a string into a DateTime object you can use the DateTime method Parse. If you had a date value stored in a string called strDate, you could turn it into a DateTime object like this:
    DateTime myDateTimeObject = DateTime.Parse(strDate);
    33. You can compare two DateTime objects by using the DateTime.Compare method. If you had two DateTime objects called dt1 and dt2 you can check to see if dt1 is greater than dt2 by doing this:
    if (DateTime.Compare(dt1,dt2) > 0)
    34. DateTime.Compare will return a 0 if the two dates are equal, a 1 if dt1 is greater than dt2, and a -1 if dt1 is less than dt2.
    35. If you put in an invalid date for either of the date fields, you will get an exception/server error when trying to parse the values. We will address this in a later lab – for now make sure you enter valid dates (valid meaning a date in the form of mm/dd/yyyy).
    36. If I had a TextBox control that was called txtAge and you wanted to set it's background color you could do this:
    txtAge.BackColor = System.Drawing.Color.Yellow;
    37. Remember to clear the PostBackURL property of the submit button!


    STEP 3: Verify and submit (10 points)
    28. View the video above on what functions your lab should have so far.
    29. Run your project. When you open the project, and go to the main menu form a record should be saved in the tblUserActivity table with the IP address, form name accessed (frmPersonnel), and the date accessed. When you click the View Activity button you should see at least one record with this information. The validation and error display should work for entering data. All navigation and hyperlinks should work.
    Once you have verified that it works, save your project, zip up all files, and submit in the Dropbox.


    NOTE: Make sure you include comments in the code provided where specified (where the " //Your comments here" is mentioned) and for any code you write, or else a five point deduction per item (form, class, function) will be made. You basically put two forward slashes, which start the comment; anything after the // on that line is disregarded by the compiler. Then type a brief statement describing what is happening in following code. Comments show professionalism and are a must in systems. As a professional developer, comments will set you apart from others and make your life much easier if maintenance and debugging are needed.

    Learn More
  8. CIS407 Lab 4 Week 4 frmMain Web Form

    CIS407 Lab 4 Week 4 Web forms with database interaction ASP.NET Web Application

    Regular Price: $12.00

    Special Price: $10.00

    This course has expired to download the latest version of CIS407A Labs click here


    CIS 407 iLab 4 of 7: Web forms with database interaction


    iLAB OVERVIEW
    Scenario/Summary
    In this lab, we will start with the form we created in Week 2 (frmPersonnel) and add functionality to INSERT records into a database table and SELECT records for display to the user. We will create a typed dataset, a Data Layer class, several functions to access the data, and a connection to a database. We also will add a search form to allow the user to search records in the database and display the results of that search.
    Instructions for Week 4 iLab: Web Forms with Database Interaction


    Deliverables
    All files are located in the subdirectory of the project. The project should function as specified: When you press the Submit button in frmPersonnel, a record should be saved in the tblPersonnel table having the FirstName, LastName, PayRate, StartDate, and EndDate you entered on the form. Add a search feature to the project. Update your main navigation page with the new options. Once you have verified that it works, save your website, zip up all files, and submit it in the Dropbox.


    iLAB STEPS
    STEP 1: Data Layer (10 points)
    1. Open Microsoft Visual Studio.NET 2008.
    2. Click the ASP.NET project called PayrollSystem to open it.
    3. Open the clsDataLayer class and add the following function:
    // This function saves the personnel data
    public static bool SavePersonnel(string Database, string FirstName, string LastName,
    string PayRate, string StartDate, string EndDate)
    {
    bool recordSaved;
    try {
    // Add your comments here
    OleDbConnection conn = new OleDbConnection("PROVIDER=Microsoft.Jet.OLEDB.4.0;" +
    "Data Source=" + Database);
    conn.Open();
    OleDbCommand command = conn.CreateCommand();
    string strSQL;
    // Add your comments here
    strSQL = "Insert into tblPersonnel " +
    "(FirstName, LastName, PayRate, StartDate, EndDate) values ('" +
    FirstName + "', '" + LastName + "', " + PayRate + ", '" + StartDate +
    "', '" + EndDate + "')";
    // Add your comments here
    command.CommandType = CommandType.Text;
    command.CommandText = strSQL;
    // Add your comments here
    command.ExecuteNonQuery();
    // Add your comments here
    conn.Close();
    recordSaved = true;
    } catch (Exception ex) {
    recordSaved = false;
    }
    return recordSaved; }
    4. In the frmPersonnelVerified form, go to the Page_Load() event and add the following code after the existing code (but in the Page_Load event handler):
    // Add your comments here
    if (clsDataLayer.SavePersonnel(Server.MapPath("PayrollSystem_DB.mdb"),
    Session["txtFirstName"].ToString(),
    Session ["txtLastName"].ToString(),
    Session ["txtPayRate"].ToString(),
    Session ["txtStartDate"].ToString(),
    Session ["txtEndDate"].ToString()))
    {
    txtVerifiedInfo.Text = txtVerifiedInfo.Text +
    "\nThe information was successfully saved!";
    }
    else
    {
    txtVerifiedInfo.Text = txtVerifiedInfo.Text +
    "\nThe information was NOT saved.";
    5. Add comments for all code containing // Add your comments here.
    6. Test your work to make sure no errors occur! (Make sure to put in valid date values for the date data entry fields).


    STEP 2: Data Display and Search (10 points)
    7. Using the skills you learned in Week 3, create a new DataSet for the tblPersonnel table (called the DataSet dsPersonnel).
    8. Using the skills you learned in Week 3, create a new function called GetPersonnel in the clsDataLayer class. This function should retrieve all data from the tblPersonnel table and return it in the form of a dsPersonnel DataSet. Use the GetUserActivity function as an example.
    9. Create a new Web form called frmViewPersonnel.
    10. Using the skills you learned in Week 3, add a GridView control (called grdViewPersonnel) to the form. This GridView control will be used to display data from the tblPersonnel table. Add the CoolBiz logo at the top of the page and make sure it links back to frmMain.
    11. Add the following code to the Page_Load() function in frmViewPersonnel:
    if (!Page.IsPostBack) {
    // Declare the DataSet
    dsPersonnel myDataSet = new dsPersonnel();
    // Fill the dataset with what is returned from the function
    myDataSet = clsDataLayer.GetPersonnel(Server.MapPath("PayrollSystem_DB.mdb"));
    // Set the DataGrid to the DataSource based on the table
    grdViewPersonnel.DataSource = myDataSet.Tables["tblPersonnel"];
    // Bind the DataGrid
    grdViewPersonnel.DataBind();
    }
    12. Return to the frmPersonnel Web form and add a button ((ID) = btnViewPersonnel, Text = View Personnel) which, when clicked, will display form frmViewPersonnel.
    13. Using the skills you learned in Week 3, open the frmPersonnelVerified form and add a button ((ID) = btnViewPersonnel, Text = View Personnel) which, when clicked, will display form frmViewPersonnel. NOTE: This is the same button with the same functionality that you added to form frmPersonnel in the previous step. Also add a new link and linked image to frmMain called View Personnel that will go to the new frmViewPersonnel page you created.
    14. You will now add a search feature to allow the user to find and display data. The user will enter a last name and the web application will display the grid of employees with all employees that match that last name.
    15. Create a new web form called frmSearchPersonnel. Add the hyperlinked Cool Biz logo to this page. Also add a new item on frmMain (with a link button and image button) called Search Personnel.
    16. On the frmSearchPersonnel form, add a label that displays "Search for employee by last name:". Next to the label, add a text box with an ID of txtSearchName. Add a button with an ID of btnSearch and set the text of the button to "Search".
    17. When the frmSearchPersonnel Search button is pressed, the frmViewPersonnel is displayed. At this point, no searching is actually happening, but you have the forms you need and the navigation working. Now you can focus on the coding you will need to do to have the grid only display matching employees.
    18. Before calling the GetPersonnel method you added previously in the lab, get the value that is in the Request["txtSearch"] item. When the form posts the search page results to the frmViewPersonnel, the name value pair for the search value is passed as part of the Request object. Assign this value to a string variable.
    19. Modify the GetPersonnel method you added to include a new parameter called strSearch of type string. This parameter needs to be after the Database string parameter that is already in the method.
    20. When calling the GetPersonnel method, pass the value you received to the strSearch parameter.
    21. In the GetPersonnel method, you now need to use the passed in strSearch parameter value as part of the SQL string being used to retrieve data. You also need to add logic so that, if strSearch is empty or has no value, all employees are returned in the query.
    22. Test the search so that when you enter a last name, employees with that last name are returned. Make sure that when you access frmViewPersonnel and you are not searching, all employees are returned.
    23. Lab Hints:
    Make sure you re-establish your database connection if you copied the files from a previous lab.
    Before you pass the search value into the GetPersonnel method, make sure you check to see if the Request item is null. If it is, you need to pass an empty string into the method or check for null inside the method. If you don't do this, you will get a server error. To check to see if an object is null, you compare the object to the keyword null.
    To create an SQL statement that will search for a given last name in the tblPersonnel table, you can do the following (assume that the search variable was called strSearch).
    "select * from tblPersonnel where LastName = '" + strSearch + "'"
    24. Add the new Search option and the View Employees option to your main navigation page.


    STEP 3: Test and submit (10 points)
    Run your project and test it as follows:
    The frmMain form should be displayed first (set this form as your start page).
    Homepage
    Click on the Add New Employee hyperlink to go to the frmPersonnel data entry form. Click the View Personnel button on this form. The frmViewPersonnel form should be displayed in the browser, but at this point, there should not be any personnel listed (because you haven't entered any yet).
    Use the Back button in your web browser to return to the frmPersonnel form and enter some personnel data, similar to the following:
    Entering Personnel Data
    Now click the Submit button. The frmPersonnelVerified form should be displayed, showing the data you entered, and you should get a message saying that the data was successfully saved, like this:
    Verifying Personnel Data
    Finally, click the View Personnel data button on this form. The frmViewPersonnel form should be displayed and should show the personnel record you just entered, retrieved from the database, like this:
    Viewing Personnel Data
    You also should be able to view the employee records by clicking the link on the home page.
    Test the search feature and make sure that entering no search string returns all the data and that typing in a last name will return all employees with the same last name.
    Search
    Search Results
    NOTE: Make sure you include comments in the code provided where specified (where the " // Your comments here" line appears) and for any code you write, or else a five point deduction per item (form, class, function) will be made.

    Learn More
  9. CIS407 Lab 5 Week 5 frmMain Web Form

    CIS407 Lab 5 Week 5 Transaction Processing ASP.NET Web Application

    Regular Price: $12.00

    Special Price: $10.00

    This course has expired to download the latest version of CIS407A Labs click here


    CIS 407 iLab 5 of 7: Transaction Processing


    iLAB OVERVIEW
    Scenario/Summary
    This week, we will use the .NET OleDbTransaction functions to either commit a set of changes to the database, if all of them were done correctly, or to roll back all of the changes if there was an error in any one of them. We will first modify the code we created last week so that it saves personnel data in the database in two steps; first by inserting a personnel record for a new employee, and then by updating that record to fill in the start and end dates. This two-step approach is not really needed in this simple case, but we will use it to simulate a more complex database transaction that would have to be done in multiple steps, such as one involving more than one table or even more than one database. We will then see what happens when there is an error in the second operation (the update), allowing a record to be created containing incomplete information--not a good result! We will fix the problem by wrapping both operations (the insert and the update) into a single transaction that will be committed (made permanent) only if both operations succeed or that will be rolled back (undone) if either operation fails. We will also add client-side validation using the ASP.Net validation controls, and we will allow the user an easy way to edit all employees.
    Instructions for Week 5 iLab: "Transaction Processing"


    Deliverables
    All files are located in the subdirectory of the project. The project should function as specified: When you press the Submit button in frmPersonnel, a record should be saved in the tblPersonnel table containing the FirstName, LastName, PayRate, StartDate, and EndDate you entered. Test that the transaction will rollback by entering invalid information in one or more items, such as Hello for a StartDate. Check tht client-side validation works: The ability to edit employees in a grid is working. Once you have verified that it works, save your website, zip up all files, and submit them to the Dropbox.


    iLAB STEPS
    STEP 1: Modify the clsDataLayer to use a two-step process (10 points)
    1. Open Microsoft Visual Studio.NET 2008.
    2. Click the ASP.NET project called PayrollSystem to open it.
    3. Open the clsDataLayer class.
    4. Modify the SavePersonnel() function so that instead of just doing a single SQL INSERT operation with all the personnel data, it does an INSERT with only the FirstName and LastName, followed by an UPDATE to save the PayRate, StartDate, and EndDate into the new record. (This two-step approach is not really necessary here because we are dealing with only one table, tblPersonnel, but we are doing it to simulate a case with more complex processing requirements, where we would need to insert or update data in more than one table or maybe even more than one database.) Find the following existing code in the SavePersonnel() function:
    // Add your comments here
    strSQL = "Insert into tblPersonnel " +
    "(FirstName, LastName, PayRate, StartDate, EndDate) values ('" +
    FirstName + "', '" + LastName + "', " + PayRate + ", '" + StartDate +
    "', '" + EndDate + "')";
    // Add your comments here
    command.CommandType = CommandType.Text;
    command.CommandText = strSQL;
    // Add your comments here
    command.ExecuteNonQuery();
    5. Modify it so that it reads as follows:
    // Add your comments here
    strSQL = "Insert into tblPersonnel " +
    "(FirstName, LastName) values ('" +
    FirstName + "', '" + LastName + "')";
    // Add your comments here
    command.CommandType = CommandType.Text;
    command.CommandText = strSQL;
    // Add your comments here
    command.ExecuteNonQuery();
    // Add your comments here
    strSQL = "Update tblPersonnel " +
    "Set PayRate=" + PayRate + ", " +
    "StartDate='" + StartDate + "', " +
    "EndDate='" + EndDate + "' " +
    "Where ID=(Select Max(ID) From tblPersonnel)";
    // Add your comments here
    command.CommandType = CommandType.Text;
    command.CommandText = strSQL;
    // Add your comments here
    command.ExecuteNonQuery();
    6. Set frmMain as the startup form and run the PayrollSystem Web application to test the changes. When valid data values are entered for a new employee, things should work exactly as they did before. To test this, enter valid data for a new employee in frmPersonnel and click Submit. The frmPersonnelVerified form should be displayed with the entered data values and a message that the record was saved successfully. Click the View Personnel button and check that the new personnel record was indeed saved to the database and that all the entered data values, including the PayRate, StartDate, and EndDate, were stored correctly. Close the browser window.
    7. Now run the PayrollSystem Web application again, but this time enter some invalid data (a nonnumeric value) in the PayRate field to cause an error, like this:
    frmPersonnel With Bad Data
    8. Click here for text description of this image.
    9. Now when you click Submit, the frmPersonnelVerified form should display a message indicating the record was not saved:
    frmPersonnel Verified With Error Message
    10. Click here for text description of this image.
    11. However, when you click on the View Personnel button to display the personnel records, you should see that an incomplete personnel record was in fact created, with missing values for the PayRate, StartDate and EndDate fields:
    Incomplete Personnel Record
    12. Click here for text description of this image.
    13. This occurred because the Insert statement succeeded but the following Update statement did not. We do not want to allow this to happen because we end up with incomplete or incorrect data in the database. If the Update statement fails, we want the Insert statement to be rolled back, or undone, so that we end up with no record at all. We will fix this by adding transaction code in the next step.


    STEP 2: Add transaction code (10 points)
    7. In the clsDataLayer.cls class file, add code to the SavePersonnel() function to create a transaction object. Begin the transaction, commit the transaction if all database operations are successful, and roll back the transaction if any database operation fails. The following listing shows the complete SavePersonnel() function; the lines you will need to add are marked with ** NEW ** in the preceding comment and are shown in bold.
    // This function saves the personnel data
    public static bool SavePersonnel(string Database, string FirstName, string LastName,
    string PayRate, string StartDate, string EndDate)
    {
    bool recordSaved;
    // ** NEW ** Add your comments here
    OleDbTransaction myTransaction = null;
    try
    {
    // Add your comments here
    OleDbConnection conn = new OleDbConnection("PROVIDER=Microsoft.Jet.OLEDB.4.0;" +
    "Data Source=" + Database);
    conn.Open();
    OleDbCommand command = conn.CreateCommand();
    string strSQL;
    // ** NEW ** Add your comments here
    myTransaction = conn.BeginTransaction();
    command.Transaction = myTransaction;
    // Add your comments here
    strSQL = "Insert into tblPersonnel " +
    "(FirstName, LastName) values ('" +
    FirstName + "', '" + LastName + "')";
    // Add your comments here
    command.CommandType = CommandType.Text;
    command.CommandText = strSQL;
    // Add your comments here
    command.ExecuteNonQuery();
    // Add your comments here
    strSQL = "Update tblPersonnel " +
    "Set PayRate=" + PayRate + ", " +
    "StartDate='" + StartDate + "', " +
    "EndDate='" + EndDate + "' " +
    "Where ID=(Select Max(ID) From tblPersonnel)";
    // Add your comments here
    command.CommandType = CommandType.Text;
    command.CommandText = strSQL;
    // Add your comments here
    command.ExecuteNonQuery();
    // ** NEW ** Add your comments here
    myTransaction.Commit();
    // Add your comments here
    conn.Close();
    recordSaved = true;
    }
    catch (Exception ex)
    {
    // ** NEW ** Add your comments here
    myTransaction.Rollback();
    recordSaved = false;
    }
    return recordSaved;
    }
    8. Run your Web application. First, enter valid data in all the fields of frmPersonnel. When you press the Submit button in frmPersonnel, a record should be saved in the tblPersonnel table containing the FirstName, LastName, PayRate, StartDate, and EndDate. With valid data entered in all the items, the "successfully saved" message should appear indicating that the transaction was committed.
    frmPersonnelVerified After Commit
    9. Click here for text description of this image.
    10. Click the View Personnel button and verify that the new record was in fact added to the database table correctly.
    frmViewPersonnel After Commit
    11. Click here for text description of this image.
    12. Now close the browser, run the Web application again, and this time test that the transaction will roll back after entering incorrect information. On the frmPersonnel form, enter invalid data for PayRate and click Submit. The "not saved" message should appear, which indicates that the transaction was rolled back.
    frmPersonnel Verified After Rollback
    13. Click here for text description of this image.
    14. Click the View Personnel button and verify that this time, as desired, an incomplete record was not added to the database table.
    frmViewPersonnel After Rollback
    15. Click here for text description of this image.
    16. You have seen how we used the try/catch block to catch an unexpected error. You may have noticed that if you enter bad data for the dates, an exception is thrown. Go back to the validation code you added in the frmPersonnel code and add a try/catch with logic to prevent an invalid date from causing a server error.
    17. In the Week 3 and Week 5 labs, you learned how to validate code once the page was posted back to the server. There is some validation that must be done on the server because it requires server resources such as the database. Some validation can also be done on the client. If you can do validation on the client it saves a round trip to the server, which will improve performance. In this approach, we will check values before the page is submitted to the server for processing. Normally, there is a combination of server and client validation used in a web application. ASP.Net includes validation controls which will use JavaScript on the client to perform validation. You will find these controls in the Validation group in the toolbox.
    18. Add validation controls to the frmPersonnel form as follows: For the first and last name, make sure each field has data in it. Use the RequiredFieldValidator for this. Add the control to the right of the text box you are validating. The location of the validator control is where the error message (if there is one) will appear for the control you link the validator to. You will be adding one validator control for each text box you want to validate. Remember to set the ControlToValidate and ErrorMessage properties on the validator control. Making this change eliminates the need for the server-side check you were doing previously. Use a regular expression validator to check that the start and end date are in the correct format.
    frmPersonnel Validation Controls
    19. Click here for text description of this image.
    20. Remove the View Personnel and Cancel buttons from the frmPersonnel form as they will cause a Postback and invoke the client-side editing you just added. The user is able to get to the View Personnel from the main form and from the personnel verification screen, so there is no need for these buttons now.
    21. Because you have entered data in this lab that is invalid and those partial records are in the database, you will need to add the ability to remove or update data. Add a new main form option called Edit Employees. Add the link and image for this. This option will take the user to a new form called frmEditPersonnel.
    frmMain with links added
    22. Click here for text description of this image.
    23. Add the new form frmEditPersonnel. On frmEditPersonnel, add the CoolBiz log at the top of the form. Add a label that says "Edit Employees." Add a GridView control with an ID of grdEditPersonnel.
    24. You will now add a SQLDataSource to the page. You will be using a databound grid for this form unlike the previous grids, in which you added as unbound (in the designer).
    25. Add a new SQLDataSource control to the frmEditPersonnel in the design view. This is not a visible control; that is, it will only appear in design view but the user will never see it. Note: If you change the folder name or location of your database, you will need to reconfigure the data source (right-click on the data source control and select the "Configure Data Source" option.
    26. There is a small > indicator in the design view of the SQL Data Source control you added if the configuration menu is collapsed (press it to open the menu), or there is a < with the menu displayed. From the data source menu, select "Configure Data Source."
    27. Press the New Connection button and select the database.
    28. Press the Next button.
    29. When asked if you want to save the connection in the application configuration file, check the Yes check box and press Next.
    30. Select the tblPersonnel table.
    31. Select all columns (you can use the * for this).
    32. Press the Advanced button and check the Generate Insert, Update, and Delete option and press the OK button.
    33. Press the Next button.
    34. Press the Test Query button and make sure everything works as it is supposed to. If it does not repeat the above steps to make sure you did everything properly. Press the Finish button.
    7. Click on the grid you added in the design view and expand the properties menu (the little > in the upper right of the control). Choose the data source you just added. On the GridView tasks menu, select Edit columns. Add an Edit, Update, and Cancel Command field. Add a Delete Command field. Press OK. You can now test the grid, which is a fully functioning Update and Delete grid. Try it out!
    Edit Employees
    8. Click here for text description of this image.
    9. Hints: Make sure you re-establish your database connection if you copied the files from a previous lab.
    In order to keep the validation controls from causing wrapping, you may want to increase the Panel width.
    A regular expression for mm/dd/yyyy is this:
    ^(0[1-9]|1[012])[- /.](0[1-9]|[12][0-9]|3[01])[- /.](19|20)\d\d$
    Experiment with the editable grid and command buttons for different display styles.


    STEP 3: Test and submit (10 points)
    29. Once you have verified that everything works as it is supposed to, save your project, zip up all files, and submit in the Dropbox.
    NOTE: Make sure you include comments in the code provided where specified (where the " // Your comments here" is mentioned) and for any code you write, or else a five point deduction per item (form, class, function) will be made.

    Learn More
  10. Programming In VB Arrays and Collections Exercise 8.1 Income Survey

    Programming In VB Arrays and Collections Exercise 8.1 Income Survey

    Regular Price: $20.00

    Special Price: $15.00

    Programming In VB Arrays and Collections Exercise 8.1 Income Survey


    8.1 Array of a structure. Create a project to analyze an income survey. The statistics for each home include an identification code, the number of members in the household, and the yearly income.
    A menu will contain File, Reports, and Help. The File menu will contain Enter Data and Exit. As the data are entered, they should be assigned from the text boxes to the elements of a structure.
    The reports for the project will be sent to the printer and include the following:
    (a) A report that displays the input data.
    (b) A listing of the identification number and income for each household that exceeds the average income.
    (c) The percentage of households having incomes below the poverty level.
    Poverty Guidelines for 2008:
    Family Size Income
    1 10210
    2 13690
    3 17170
    4 20650
    5 24130
    6 27610
    7 31090
    8 34570
    For each additional Person add 3480


    Test Data
    ID Number Number of Persons Annual Income
    2497 2 32500
    3323 5 23000
    4521 4 38210
    6789 2 38000
    5476 1 26000
    4423 3 16400
    6587 4 25000
    3221 4 20500
    5555 2 18000
    0085 3 19700
    3097 8 30000
    4480 5 23400
    0265 2 19700
    8901 3 13000

    Learn More

Items 41 to 50 of 181 total

per page
Page:
  1. 3
  2. 4
  3. 5
  4. 6
  5. 7

Grid  List 

Set Ascending Direction