please give me sample code for insert data to MS ACCESS from grid view using dataset
View Complete Post
I am trying to insert data to Excel Document using OLEDB as follows:-
sql = "Insert into [MyFirstSheet$] (" + Title1 + "," +Title2 + "," + Title3 + ")
values('" + Value1 + "','" + Value2 + "','" + Value2 + "')";
myCommand.CommandText = sql;
But, the Title1 ,Title2, Title3 are in the 3rd row of the Excel Document. So, the data is not inserted.
I was rummaging the internet learning aspx and came across the concept of: Microsoft Application Block for Data Access in .NET
It seems great of course. The articles are all early 2003-5 such as
So the question is - is this tech still relevant and should I be using it?
Ive just started a project that will use the enterprise library 4.1 data access code blocks. Its been years since ive used them, can anyone tell me what assemblies I need to reference in my project in order to use them ? Ive referenced
are there any others I need ?
Julie Lerman shows database administrators how to limit access to databases from the Entity Framework by allowing it to work only with views and stored procedures instead of tables-without impacting application code or alienating developers.
MSDN Magazine August 2010
Building an NHibernate-based desktop application isn't any harder than building a web application, and in many cases NHibernate simplifies elements of session handling and concurrency.
MSDN Magazine December 2009
Developers deploy a wide variety of development philosophies and architecture styles. This article explores three common perspectives on application development and describes how the Entity Framework can be employed in each. Specifically, the article looks at the forms-centric, model-centric, and code-centric development styles and their relationship to the Entity Framework.
MSDN Magazine August 2009
In this article, the author delves into some commonly used ways of writing data access code and looks at the effect they can have on performance.
In this article the author looks at two versions of the same application--one consuming an on-premise Data Service, and one consuming an Azure Table Data Service to illustrate data access in the cloud.
MSDN Magazine May 2009
Building a data access layer using LINQ to SQL and the ADO.NET Entity Framework allows you to decouple your application from the persistence technology you're using.
MSDN Magazine December 2008
ADO. NET 2. 0 sports some exciting enhancements to the core classes found in ADO. NET 1. x and introduces a variety of new classes, all of which promise to improve performance, flexibility, and efficiency.
MSDN Magazine November 2005
E nterprise applications can have a wide variety of data update requirements. Sometimes you need to save multiple rows of changes at once within a single transaction. Other times, the user must be allowed to enter multiple rows of data, send them to the database in a batch; and if a row or two fails, only the rows that succeeded should be committed and remain committed.
MSDN Magazine October 2005
Last month I explored the foundation of the Enterprise Library Data Access Application Block (DAAB) including how it all fits into an architecture (see Data Points: The Enterprise Library Data Access Application Block, Part 1).
MSDN Magazine August 2005
A solid data access later (DAL) can benefit an application by hiding redundant tasks, helping handle exceptions more gracefully, helping clean up resources more efficiently, and providing a layer of abstraction from the database.
MSDN Magazine July 2005
When your goal is a scalable and efficient enterprise solution, you need to develop an efficient data-access strategy. You can't just do some testing on your production machines and rely on the results.
MSDN Magazine May 2005
MSDN Magazine June 2004