Wrox Programmer Forums
Go Back   Wrox Programmer Forums > C# and C > C# 1.0 > C#
C# Programming questions specific to the Microsoft C# language. See also the forum Beginning Visual C# to discuss that specific Wrox book and code.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the C# section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old July 2nd, 2004, 09:58 AM
Registered User
Join Date: Jul 2004
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default Best practice for database calls

I asked the following question in another forum, and got a response that I thought was good, but still need some guidance.

My Question
I'm new to C# and to Object Oriented programming. I have some experience using ASP and limited experience with VBA and VB 6.0.

In an effort to learn I'm toying around with building an Iventory Management application. For the purposes of this question, lets say I have two classes, an Item Class and an Inventory Class, each which will be used to manupulate data in an Access database.

What is the best way to structure the calls to the database for Inserts, updates and deletions (where should they physically be within my class structure)?

Will all my data access be contained in one class, or should they reside in the other classes (Item and Inventory, etc.). Any help or guidance or examples would be apprecieted.

The response:

************************************************** ******************
There are as many different ways to do what your asking as there are programmers...

But here is how I do it...

I have a web project in a solution that consumes object defined in a Class Library project. In my class library project I have 2 folders. One called BLL, for Business Logic Layer. And one called DAL, for Data Access Layer.

In my BLL folder, I would put the 2 classes you talked about, Item and Inventory.

In the DAL folder I would have 2 additional classes. One called DataSource, and one called Configuration. Each of these contains static member functions and properties to facilitate talking to the database, and getting configuration information.

I use the Configuration class to get things like connection strings, email servers, administrator email address, and other configuration information so that it isn't compiled in the application. You can store this kind of thing in the web.config, or the app.exe.config file then I use the Configuration class to go get them.

The DataSource class in my app would have several static properties.

One called ItemAdapter, initialized with this code...

public static SqlDataAdapter ItemAdapter{
SqlDataAdapter Adapter = new SqlDataAdapter(
"SELECT * FROM MyItemTable",
new SqlConnection(Configuration.DatabaseConnectionStri ng));

SqlCommandBuilder Builder = new SqlCommandBuilder(Adapter);
Adapter.InsertCommand = Builder.GetInsertCommand();
Adapter.UpdateCommand = Builder.GetUpdateCommand();
Adapter.DeleteCommand = Builder.GetDeleteCommand();

return Adapter;

Then, my DataSource class would have the following property

public static DataSet ItemData
DataSet AlloSet = new DataSet("ItemData");

DataSource.ItemAdapter.Fill(AlloSet, "ItemData");

return AlloSet;

Then you create similar properties for your Inventory class.

These give you the basis of the most important ADO.NET objects, and a decent way to access them.

Then, my Item and Inventory classes would each have a Constructor that accepts an ID and would go talk to the DataSource class to get a DataRow object and populate itself. They also would have Insert, Update, and Delete Functions that would also go talk to the DataSource class and perform those pieces of functionality.

You could then implement caching in ASP.NET or use Global variables in Windows forms to minimize the number of database calls, and the number of times you have to construct your ADO.NET objects.

Also, ADO DataSets are not the fastest way of getting data out of a database. If performance is a big deal, then you might want to use SqlDataReader's. They are the fastest way of getting data out of a database. Like this...

public static SqlDataReader ItemReader
return DataSource.ItemAdapter.SelectCommand.ExecuteReader ();

************************************************** *******************
I'm trying to use the example above and add a neew record to the Item table described in my original question. I've done some fooling around, and some looking but the examples I've seen don't fit into this mold..

Can anyone PLEASE point me int the right direction?


AKA Beerman...The great American Homebrewer

Similar Threads
Thread Thread Starter Forum Replies Last Post
An error for AJAX practice wen BOOK: Beginning Ajax with ASP.NET 0 December 13th, 2006 06:02 PM
practice help with C++ mastrgamr C++ Programming 2 November 2nd, 2006 07:55 AM
Looking for some practice Vano2005 C++ Programming 2 July 7th, 2005 04:30 PM
regular expression/general practice dungey Pro PHP 5 November 5th, 2004 09:35 AM
Best practice of Passing Parameters for a report? segeller Crystal Reports 1 August 29th, 2003 01:08 AM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.