Words: 1213
Introduction and Rationale During Week 1, the primary learning activity is to set up the programming and database environments that you will use in completing the course labs. We will investigate TCO 5 by learning how to use Visual Studio to connect to a Myself database. This setup will be tested by a short C#. NET program that will query and display data from a Myself table. You will then be asked to modify this program to display additional information. TCO 1 will be addressed as you begin to design your project requirements document that constitutes the class project.
Teams of two or three should be assigned by our instructor so that you can begin collaborating on this project. Lab Steps Step I?setting up Myself For Week 1, you will create a Myself database that is typical of an inventory management system. The entity relationship diagram (RED) is shown in Figure Figure 1 – Inventory Database RED To use Myself in this course, a third-party service called Omnibus has been employed to provide virtual Myself servers. You should have been assigned a user ID and password for this service.
Omnibus is a typical online service like those that many companies use for application and website development. Learning to use Omnibus is an important activity that can serve you well both academically and professionally. This being said, some students may find that they want to install Myself on their personal computer. The community edition of Myself is free. With the permission of the instructor, the saws student could setup and use Myself on their personal computer system fairly easily?however, this is beyond the scope of the course.
Technical support WILL NOT be provided by Diver or your professor if you choose to set up Myself on your personal system. Additionally, all of the examples given in the course use the Omnibus erosion of Myself server. The steps for setting up your Week 1 lab Myself database on Omnibus can be found in Document Sharing in the document entitled: ASSAYS_Online_Database_setup. Doc Step 2?Visual Studio connectivity and testing This course will use Microsoft’s C#. NET, which is part of the Visual Studio package. Using C_# will provide a relatively easy method for connecting your programs to the data.
Setting up such a connection in the real world is always a complicated task the first time, but most businesses have established a repeatable method which they use over and over again in their projects. You will be provided with a method of connecting C#. NET with Myself using ODBC, but you should be aware that there are several other techniques that work equally well. ODBC is a Microsoft middleware technology that works well with products like C# and Java. The steps for setting up and testing you connectivity between C#.
NET and Myself can be found in Document Sharing in the document entitled: ASSAYS_Claret_Programming_setup. Doc Step 3?Reading and displaying data from a relational database. During Step 2, you created and tested a program that displayed several item ID numbers from the Item table. Not only did this test your ability to copy and run a C# program, but also proved that you successfully connected to the Myself database on the Omnibus server. For your next step, you will create a typical relational query that is somewhat more complex, yet based upon these concepts.
Modify the program provided in Step 2 to display the following information on the console with a simple column header: Item Description quantity in inventory size of item color Of item price of item See Figure 1 above for the database RED. You will need to “join” the item and inventory tables with your embedded SQL query. Figure 2 shows the expected console output: Figure 2? Console output from lab 1 Console Output: ITEM Season Tent 200 S Khaki QUANT SIZE COLOR PRICE – 3-Season Tent 200 Sienna $259. 99 3- Forest $259. 9 Women’s Hiking Shorts $29. 95 Women’s Hiking Shorts 200 M Khaki 200 L Khaki $29. 95 Women’s Hiking Shorts S Olive $29. 95 Women’s Hiking Shorts M Olive $29. 95 Women’s Hiking Shorts L Love $29. 95 Women’s Fleece Pullover S Teal $59. 95 Women’s Fleece Pullover M Teal $59. 95 Children’s Beachcomber Sandals 200 10 Blue $15. 99 Children’s Beachcomber Sandals 200 12 Blue $15. 99 Children’s Beachcomber Sandals 200 1 Red $15. 99 Mess Expedition parka S Navy $199. 95 Mess Expedition Parka 200 M Navy $199. 95 Mess Expedition Parka 200 XSL Navy $209. 5 Deliverables For lab 1, you will submit the following deliverables to the course Dropped in a single Microsoft Word for Windows document: 1. Name your file Lasted_Firsthand_WWW_lab. Doc. If your instructor requests additional files, you can ZIP this into a file entitled: _lab. Zip. 2. In the document, include your full name, course number, professors name, date, assignment number, and email address as a header. 3. Include a screen capture of the console output. You can capture the console window by holding down the ALT key and pressing Print Screen.
This will place the console window on the clipboard. You can then paste it into Word. 4. Copy and paste the program code into Word after the screen capture. Your instructor may ask you to include your entire project as a ZIP file. If so, she or he will give you specific instructions. Make sure you close and save your Word document before uploading it to the Dropped. This will ensure that the latest version of the file is uploaded. Grading Rubric lab Deliverables points Item 1 Document header and comments in the code. 10 Item 2 Well written and functional C#. NET program. 0 Item 3 Proper values in output screenings. Item 4 Item 3 is well formatted as in the sample output from Figure 2 above. 10 Total Points 50 Hints and Tips HINT 1: Be sure to use the program in the Vision Setup document ASSAYS CITRIC_Programming_setup. Doc as a starting point for your program. HINT 2: Here is an example embedded SQL query that joins two tables dealing with employees and their department name. Your query will be similar but deal with the item and inventory tables. String together = “SELECT lasted, firsthand, ample, department_des ” department ‘ “FROM employee, + “WHERE employee. Apartment_old = department. Department_id”; There are several things to notice here. The first is that the department description is contained within the department table which must be joined to the employee table which only has the department ID. The join is accomplished by matching the IDs within the WHERE clause. The next thing to notice is that there is a space at the end of the first two lines before the quotation closes. Why? Failure to include this space would cause the SQL statement to contain “department_decorum employee”, which is obviously going to create an error.
Some students find that it is a good habit to print Out together to console while they are developing the program so that they can “eyeball” the embedded SQL and check for errors. Console. Written(together); This SQL can certainly be written in different ways. An alternative might be: string together = “SELECT a. lasted, a. firsthand, a. ample, b. Department_des ‘ + “FROM employee a, department b + “WHERE a. Department_old b. Department_id”; Using the table. Column format with table labels often clears up arbitrary assignments, but in the previous example it was only needed for the WHERE clause.