|TOTAL: 9 Page: 1 of 1||
Creating a general data component for OleDb and Sql
While you should define your data requirements at the beginning of your development phase, sometimes you may have to move back and forth between a Sql connection and an OleDb connection. This example walks you through creating a general data component that you can use to switch back and forth between Sql and OleDb DataReaders and Collections, as well as allowing the flexibility of using either keys in the Web.Config file, or by providing a custom Connection String. In our example we'll be usi
Database Access Class
The following is database helper class. Plug it in to your existing .cs files, making sure to rename the namespace to match your current one. There are overloaded functions so you can call functions that return data, some that don't. You can call stored procedures that require input parameters and some that don't.
Build Your Own Reusable Datalist with VS.NET
In my previous contribution The Datagrid Revisited: Editing a Live Database in Template Columns, I spent some time working with the datagrid control to browse and edit database data. In the article, I had used template columns to customize columns of the grid. The datagrid's sibling in the framework is the datalist. At first instance it looks like a datagrid with only one column, which is a template column. The control has a large number of different items, from header to selected item. As all i
Inside .NET Managed Providers
When compared to full-fledged OLE DB providers, Microsoft .NET managed providers have a lot to offer. First off, they deliver a simplified data access architecture that often results in improved performance without the loss of functional capabilities. Furthermore, .NET managed providers directly expose provider-specific behavior to consumers through methods and properties. They also involve a much smaller set of interfaces than OLE DB providers. Last but not least, .NET managed providers work wi
The ODBC .NET Data Provider is an add-on component to the Microsoft .NET Framework Software Development Kit (SDK). It provides access to native ODBC drivers the same way that the OLE DB .NET Data Provider provides access to native OLE DB Providers. Although the ODBC .NET Data Provider is intended to work with all compliant ODBC drivers, it has only been tested with the following drivers: -Microsoft SQL ODBC Driver -Microsoft ODBC Driver for Oracle -Microsoft Jet ODBC Driver As popular
Connecting to a text file using ADO.NET
After playing around with ADO.NET and getting an important question answered from the ADOGuy site. I was able to piece together how to use ODBC with a text file in .NET. The first step is to create a Data Source Name (DSN) in order to connect through ODBC. This can be done by bringing up the ODBC Drivers Administration tool through the control panel.
Open a SQL Server Database
This article describes how you can use ADO.NET to open a SQL Server database by using the SQL Server .NET data provider. ADO.NET gathers all of the classes that are required for data handling. The System.Data.SqlClient namespace describes a collection of classes that are used to programmatically access a SQL Server data source. You can access ADO classes through the System.Data.OleDb namespace to provide support for OLE DB databases. In this article, connections are set up both programmatical
Obtain Underlying Provider Errors
Managed providers can raise several exceptions. To obtain more detailed information about the cause, you need access to provider-specific error information.
Creating a DSN
This tutorial will instruct you on how to create a simple DSN connection to an Access database, but the same concepts apply for connecting to any other database through a DSN connection.