SlideShare a Scribd company logo
systems lab
Once the Application has started up and you are at the Start
Page, select the create a new project option. When presented
with the New Project window like the one below, be sure that
you have highlighted Console Application under the Templates
window. Now give the new project the name INV_GRAB in the
Name field, and have the location field pointing to the
F:SAI430 folder you have on the F: drive. The diagram below
depicts what your New Project window should look similar to.
Once you have done this, select OK to complete this operation.
You may get a "Microsoft Development Environment" message
box stating that the project location is not a fully trusted .NET
runtime location. You can ignore this and just select OK. You
should now see your new project listed in the
Solution
Explorer window on the upper right hand corner of the editor
window. You are now ready to begin setting up your form.
STEP 2: Setting Up a Database Connection
Back to Top
The first step now is to set up a database connection with
Access and then a data set that can be used to transport the data
from the database to the application to be written to a file. For
the purposes of this lab and your project, you will only need
data from two columns in the ITEMS table of the INVENTORY
database, but we will control that with the code written later.
The following steps will lead you through the process of setting
up the connection.
To begin, you need to add the following three namespaces to the
top of your application code:
using System.IO;
using System.Data;
using System.Data.OleDb;
Since you are going to be not only connecting to a database but
also writing data to a file, you will need all three of these listed.
Now you can set up the connection to your Access database that
you downloaded and put in your folder. The actual connection
string is @"Provider=Microsoft.JET.OLEDB.4.0; data
source=F:inventory.mdb". This is a standard connection string
for MS Access. You will want to precede this with the command
- string conString = so that the finished connection looks like
this.
string conString = @"Provider=Microsoft.JET.OLEDB.4.0; data
source=F:SAI430inventory.mdb";
This is simply defining a string variable named conString and
assigning the connection string to it. We will use this variable
later.
Now we need to define an OleDbConnection that will be used to
connect to the database. To do this you will need to define a
connection variable as a new OleDbConnection and point it to
the connection string defined in the previous step. Your code
should look like the following.
OleDbConnection conn = new OleDbConnection(conString);
Now you can connect and open the database with the following
command entered right below the line above.
conn.Open();
Last, we need to declare a variable that will be used later on.
Although this really has nothing to do with setting up the
database connection, this is as good a place as any to do this.
You need to define a single variable named rowCount as an
integer and initialize it to zero. Your code should look like the
following.
int rowCount = 0;
STEP 3: Setting Up a Data Set
Back to Top
Now you will need to set up a Data Set that will be used to hold
the data that is pulled from the database so that it can be
processed. This dataset will hold all of the records from the
item table. We will use this data to write out our inventory list
to a file.
You will need to create a query string that will be used to get
the data in the "item" table. This will be a simple select
statement that will get all of the data from the table (we will be
specific regarding what is needed later). You will need to define
a string variable for this query string similar to what you did for
the connection string. When finished, your new string should
look like the following:
string selectStr = "SELECT * FROM item";
There is a variable we will need to use later on, so we might as
well define and initialize at this point. The new variable is an
integer data type and needs to be named rowCount. Initialize it
to zero.
Now you need a new OleDbDataAdapter to work with the
dataset. To do this you will need to define an object named
DataAdapter as a new OleDbDataAdapter and then use the
selectStr created above and the connection variable create to
load it. Your code should look like the following:
OleDbDataAdapter DataAdapter = new
OleDbDataAdapter(selectStr, conn);
Now we can define the data set like the following:
DataSet dataSet = new DataSet();
This is a simple definition that we can use along with the
DataAdapter Fill method to fill the data set like the following:
DataAdapter.Fill(dataSet, "item");
We now have one more step that will allow us to define which
columns we want to get data from later on. We need to define a
DataTable object based on the new dataSet. To do this you will
need the following code:
DataTable dataTable = dataSet.Tables[0];
STEP 4: Getting and Writing the Data
Back to Top
So far we have put everything together to get the data from the
database into our program. Now we need to deal with writing
the data out to a file. To do this we will be using the
StreamWriter class and some of its objects.
We must declare a new instance of the StreamWriter so that we
can obtain its methods. At the same time we can also initialize
the new writer to point to where we want the file to be written
to. Your code should look like the following.
StreamWriter sw = new
StreamWriter(@"F:sai430INV_GRB.txt", false);
Now we are ready to set up the processing to loop through our
data set, pull the data we need into a file, and print it out. To
help with this there is a file in Doc Sharing named
Lab1_code.txt. The code in this file can be copied and pasted
into the area of the code section you are working, just below the
line you added above. Be sure to change the directory path to
match yours for the output file.
You are now ready to make your last build. If everything has
been done correctly, you should end up with no error messages
and clean build. Once this has been done then you are ready to
execute the application by selecting Debug => Start from the
main menu. If all goes well you should be able to find your
output file in the location listed in the program.
STEP 5: Building the Application
Back to Top
You are now ready to make your last build, but first you need to
make two changes to the properties for your project.
Changing the build option for 32-bit.
We need to build the application as a 32-bit application so it
will work with the Microsoft ODBC drivers for Access; to do
this you will need to select
Project => INV_GRAB Properties
from the main menu. Now select the Build tab on the side of
the properties box, and then in the drop down list next to
Program Target, select the X86 option. This will allow the
application to build as a 32-bit application. Do not close the
properties window yet though, because there is one more step.
Setting the Security option:
Now select the Security tab on the left side. Check the
Enable ClickOnce Security Settings
check box. This is a full trust application option, which is what
you want.
Now select
File => Save All
from the main menu and then close the properties window.
Now you can either build or re-build the application. If
everything has been done correctly, you should end up with no
error messages and clean build. Once this has been done, you
are ready to execute the application by selecting Debug => Start
from the main menu. If all goes well you should be able to find
your output file in the location listed in the program.
STEP 6: Testing Your Application
Back to Top
You first want to make sure that you have the Inventory.MDB
database in the SAI430 folder on the F: of your directory
structure in Citrix. This should also be the same location of
your source code project and the location to which you have
pointed the program to write the output file. In order to test the
application and generate the output document you will need to
turn in, do the following:
Again, make sure the application, inventory.mdb, and the output
path in the application are all using the SAI430 directory on the
F: drive in Citrix.
Execute your program.
Check to make sure that the output file has the correct data in it.
Submit this file along with your code to be graded

More Related Content

DOCX
Once the Application has started up and you are at the Start Page, s.docx
DOCX
EN1320 Module 2 Lab 2.1Capturing the Reader’s InterestSelec.docx
PPT
Database Connection
DOCX
Window programming
DOCX
Simple ado program by visual studio
DOCX
Simple ado program by visual studio
PDF
Access 2003 tutorial 2
PDF
Ado.Net
Once the Application has started up and you are at the Start Page, s.docx
EN1320 Module 2 Lab 2.1Capturing the Reader’s InterestSelec.docx
Database Connection
Window programming
Simple ado program by visual studio
Simple ado program by visual studio
Access 2003 tutorial 2
Ado.Net

Similar to systems labOnce the Application has started up and you are at the .docx (20)

PPTX
PATTERNS07 - Data Representation in C#
PDF
Pharmacy management system project report..pdf
PDF
Bt0082 visual basic2
PPT
VB Dot net
PPTX
Welcome-slides-durham-tech
DOC
Abap performance
DOCX
Ms Access
PDF
PDF
Access Tutorial
PDF
Access tutorial
DOCX
CS 2336 PROJECT 3 – Linked Inventory Management Project Due 1104 b.docx
DOCX
Machine problems
DOCX
DOCX
data binding.docx
PDF
Project report
PDF
An introduction to_application_development_in_ibm_db2_udb_using_microsoft_vis...
PDF
IBM DB2 App Development with Microsoft Visual C#
DOCX
Visual basic bt0082
PDF
5c8605.ado.net
DOC
124157075 gb
PATTERNS07 - Data Representation in C#
Pharmacy management system project report..pdf
Bt0082 visual basic2
VB Dot net
Welcome-slides-durham-tech
Abap performance
Ms Access
Access Tutorial
Access tutorial
CS 2336 PROJECT 3 – Linked Inventory Management Project Due 1104 b.docx
Machine problems
data binding.docx
Project report
An introduction to_application_development_in_ibm_db2_udb_using_microsoft_vis...
IBM DB2 App Development with Microsoft Visual C#
Visual basic bt0082
5c8605.ado.net
124157075 gb

More from perryk1 (20)

DOCX
Take a few moments to research the contextual elements surrounding P.docx
DOCX
Table of Contents Section 2 Improving Healthcare Quality from.docx
DOCX
Take a company and build a unique solution not currently offered. Bu.docx
DOCX
Tackling a Crisis Head-onThis week, we will be starting our .docx
DOCX
take a look at the latest Presidential Order that relates to str.docx
DOCX
Table of Contents-Perioperative Care.-Perioperative Med.docx
DOCX
Take a look at the sculptures by Giacometti and Moore in your te.docx
DOCX
Table of ContentsLOCAL PEOPLE PERCEPTION TOWARDS SUSTAINABLE TOU.docx
DOCX
Table of Contents Title PageWELCOMETHE VAJRA.docx
DOCX
Take a few minutes to reflect on this course. How has your think.docx
DOCX
Taiwan The Tail That Wags DogsMichael McDevittAsia Po.docx
DOCX
TABLE 1-1 Milestones of Medicine and Medical Education 1700–2015 ■.docx
DOCX
Tackling wicked problems A public policy perspective Ple.docx
DOCX
Tahira Longus Week 2 Discussion PostThe Public Administration.docx
DOCX
Tabular and Graphical PresentationsStatistics (exercises).docx
DOCX
Table 4-5 CSFs for ERP ImplementationCritical Success Fact.docx
DOCX
Table 7.7 Comparative Financial Statistics Universal Office Fur.docx
DOCX
TableOfContentsTable of contents with hyperlinks for this document.docx
DOCX
Tajfel and Turner (in chapter two of our reader) give us the followi.docx
DOCX
tabOccupational Safety & Health for Technologists, Enginee.docx
Take a few moments to research the contextual elements surrounding P.docx
Table of Contents Section 2 Improving Healthcare Quality from.docx
Take a company and build a unique solution not currently offered. Bu.docx
Tackling a Crisis Head-onThis week, we will be starting our .docx
take a look at the latest Presidential Order that relates to str.docx
Table of Contents-Perioperative Care.-Perioperative Med.docx
Take a look at the sculptures by Giacometti and Moore in your te.docx
Table of ContentsLOCAL PEOPLE PERCEPTION TOWARDS SUSTAINABLE TOU.docx
Table of Contents Title PageWELCOMETHE VAJRA.docx
Take a few minutes to reflect on this course. How has your think.docx
Taiwan The Tail That Wags DogsMichael McDevittAsia Po.docx
TABLE 1-1 Milestones of Medicine and Medical Education 1700–2015 ■.docx
Tackling wicked problems A public policy perspective Ple.docx
Tahira Longus Week 2 Discussion PostThe Public Administration.docx
Tabular and Graphical PresentationsStatistics (exercises).docx
Table 4-5 CSFs for ERP ImplementationCritical Success Fact.docx
Table 7.7 Comparative Financial Statistics Universal Office Fur.docx
TableOfContentsTable of contents with hyperlinks for this document.docx
Tajfel and Turner (in chapter two of our reader) give us the followi.docx
tabOccupational Safety & Health for Technologists, Enginee.docx

Recently uploaded (20)

PPTX
PPH.pptx obstetrics and gynecology in nursing
PDF
BÀI TẬP BỔ TRỢ 4 KỸ NĂNG TIẾNG ANH 9 GLOBAL SUCCESS - CẢ NĂM - BÁM SÁT FORM Đ...
PPTX
Microbial diseases, their pathogenesis and prophylaxis
PDF
Classroom Observation Tools for Teachers
PPTX
Pharma ospi slides which help in ospi learning
PDF
Insiders guide to clinical Medicine.pdf
PDF
The Lost Whites of Pakistan by Jahanzaib Mughal.pdf
PDF
Module 4: Burden of Disease Tutorial Slides S2 2025
PDF
2.FourierTransform-ShortQuestionswithAnswers.pdf
PPTX
Renaissance Architecture: A Journey from Faith to Humanism
PDF
Abdominal Access Techniques with Prof. Dr. R K Mishra
PDF
FourierSeries-QuestionsWithAnswers(Part-A).pdf
PDF
ANTIBIOTICS.pptx.pdf………………… xxxxxxxxxxxxx
PDF
Complications of Minimal Access Surgery at WLH
PDF
01-Introduction-to-Information-Management.pdf
PDF
102 student loan defaulters named and shamed – Is someone you know on the list?
PDF
grade 11-chemistry_fetena_net_5883.pdf teacher guide for all student
PPTX
1st Inaugural Professorial Lecture held on 19th February 2020 (Governance and...
PPTX
IMMUNITY IMMUNITY refers to protection against infection, and the immune syst...
PDF
Computing-Curriculum for Schools in Ghana
PPH.pptx obstetrics and gynecology in nursing
BÀI TẬP BỔ TRỢ 4 KỸ NĂNG TIẾNG ANH 9 GLOBAL SUCCESS - CẢ NĂM - BÁM SÁT FORM Đ...
Microbial diseases, their pathogenesis and prophylaxis
Classroom Observation Tools for Teachers
Pharma ospi slides which help in ospi learning
Insiders guide to clinical Medicine.pdf
The Lost Whites of Pakistan by Jahanzaib Mughal.pdf
Module 4: Burden of Disease Tutorial Slides S2 2025
2.FourierTransform-ShortQuestionswithAnswers.pdf
Renaissance Architecture: A Journey from Faith to Humanism
Abdominal Access Techniques with Prof. Dr. R K Mishra
FourierSeries-QuestionsWithAnswers(Part-A).pdf
ANTIBIOTICS.pptx.pdf………………… xxxxxxxxxxxxx
Complications of Minimal Access Surgery at WLH
01-Introduction-to-Information-Management.pdf
102 student loan defaulters named and shamed – Is someone you know on the list?
grade 11-chemistry_fetena_net_5883.pdf teacher guide for all student
1st Inaugural Professorial Lecture held on 19th February 2020 (Governance and...
IMMUNITY IMMUNITY refers to protection against infection, and the immune syst...
Computing-Curriculum for Schools in Ghana

systems labOnce the Application has started up and you are at the .docx

  • 1. systems lab Once the Application has started up and you are at the Start Page, select the create a new project option. When presented with the New Project window like the one below, be sure that you have highlighted Console Application under the Templates window. Now give the new project the name INV_GRAB in the Name field, and have the location field pointing to the F:SAI430 folder you have on the F: drive. The diagram below depicts what your New Project window should look similar to. Once you have done this, select OK to complete this operation. You may get a "Microsoft Development Environment" message box stating that the project location is not a fully trusted .NET runtime location. You can ignore this and just select OK. You should now see your new project listed in the Solution Explorer window on the upper right hand corner of the editor window. You are now ready to begin setting up your form. STEP 2: Setting Up a Database Connection Back to Top The first step now is to set up a database connection with Access and then a data set that can be used to transport the data from the database to the application to be written to a file. For the purposes of this lab and your project, you will only need data from two columns in the ITEMS table of the INVENTORY database, but we will control that with the code written later. The following steps will lead you through the process of setting
  • 2. up the connection. To begin, you need to add the following three namespaces to the top of your application code: using System.IO; using System.Data; using System.Data.OleDb; Since you are going to be not only connecting to a database but also writing data to a file, you will need all three of these listed. Now you can set up the connection to your Access database that you downloaded and put in your folder. The actual connection string is @"Provider=Microsoft.JET.OLEDB.4.0; data source=F:inventory.mdb". This is a standard connection string for MS Access. You will want to precede this with the command - string conString = so that the finished connection looks like this. string conString = @"Provider=Microsoft.JET.OLEDB.4.0; data source=F:SAI430inventory.mdb"; This is simply defining a string variable named conString and assigning the connection string to it. We will use this variable later. Now we need to define an OleDbConnection that will be used to connect to the database. To do this you will need to define a connection variable as a new OleDbConnection and point it to the connection string defined in the previous step. Your code should look like the following.
  • 3. OleDbConnection conn = new OleDbConnection(conString); Now you can connect and open the database with the following command entered right below the line above. conn.Open(); Last, we need to declare a variable that will be used later on. Although this really has nothing to do with setting up the database connection, this is as good a place as any to do this. You need to define a single variable named rowCount as an integer and initialize it to zero. Your code should look like the following. int rowCount = 0; STEP 3: Setting Up a Data Set Back to Top Now you will need to set up a Data Set that will be used to hold the data that is pulled from the database so that it can be processed. This dataset will hold all of the records from the item table. We will use this data to write out our inventory list to a file. You will need to create a query string that will be used to get the data in the "item" table. This will be a simple select statement that will get all of the data from the table (we will be specific regarding what is needed later). You will need to define a string variable for this query string similar to what you did for the connection string. When finished, your new string should look like the following:
  • 4. string selectStr = "SELECT * FROM item"; There is a variable we will need to use later on, so we might as well define and initialize at this point. The new variable is an integer data type and needs to be named rowCount. Initialize it to zero. Now you need a new OleDbDataAdapter to work with the dataset. To do this you will need to define an object named DataAdapter as a new OleDbDataAdapter and then use the selectStr created above and the connection variable create to load it. Your code should look like the following: OleDbDataAdapter DataAdapter = new OleDbDataAdapter(selectStr, conn); Now we can define the data set like the following: DataSet dataSet = new DataSet(); This is a simple definition that we can use along with the DataAdapter Fill method to fill the data set like the following: DataAdapter.Fill(dataSet, "item"); We now have one more step that will allow us to define which columns we want to get data from later on. We need to define a DataTable object based on the new dataSet. To do this you will need the following code: DataTable dataTable = dataSet.Tables[0]; STEP 4: Getting and Writing the Data Back to Top So far we have put everything together to get the data from the
  • 5. database into our program. Now we need to deal with writing the data out to a file. To do this we will be using the StreamWriter class and some of its objects. We must declare a new instance of the StreamWriter so that we can obtain its methods. At the same time we can also initialize the new writer to point to where we want the file to be written to. Your code should look like the following. StreamWriter sw = new StreamWriter(@"F:sai430INV_GRB.txt", false); Now we are ready to set up the processing to loop through our data set, pull the data we need into a file, and print it out. To help with this there is a file in Doc Sharing named Lab1_code.txt. The code in this file can be copied and pasted into the area of the code section you are working, just below the line you added above. Be sure to change the directory path to match yours for the output file. You are now ready to make your last build. If everything has been done correctly, you should end up with no error messages and clean build. Once this has been done then you are ready to execute the application by selecting Debug => Start from the main menu. If all goes well you should be able to find your output file in the location listed in the program. STEP 5: Building the Application Back to Top You are now ready to make your last build, but first you need to
  • 6. make two changes to the properties for your project. Changing the build option for 32-bit. We need to build the application as a 32-bit application so it will work with the Microsoft ODBC drivers for Access; to do this you will need to select Project => INV_GRAB Properties from the main menu. Now select the Build tab on the side of the properties box, and then in the drop down list next to Program Target, select the X86 option. This will allow the application to build as a 32-bit application. Do not close the properties window yet though, because there is one more step. Setting the Security option: Now select the Security tab on the left side. Check the Enable ClickOnce Security Settings check box. This is a full trust application option, which is what you want. Now select File => Save All from the main menu and then close the properties window. Now you can either build or re-build the application. If everything has been done correctly, you should end up with no error messages and clean build. Once this has been done, you are ready to execute the application by selecting Debug => Start from the main menu. If all goes well you should be able to find your output file in the location listed in the program.
  • 7. STEP 6: Testing Your Application Back to Top You first want to make sure that you have the Inventory.MDB database in the SAI430 folder on the F: of your directory structure in Citrix. This should also be the same location of your source code project and the location to which you have pointed the program to write the output file. In order to test the application and generate the output document you will need to turn in, do the following: Again, make sure the application, inventory.mdb, and the output path in the application are all using the SAI430 directory on the F: drive in Citrix. Execute your program. Check to make sure that the output file has the correct data in it. Submit this file along with your code to be graded