data access layer

[SqlJunkies User]

Is anyone working with a data access blocks /layer to .NET Maybe I'm just not getting it but how does it work. The way I understand the data access layer/block is that they leave all the database functionallity out of the database. Generice objects are setup for connections to the database(Update, Read, Write, delete). With that being the case I would have a generice access block for tables, views, stored procedures, roles, rules and users. As long as the developers can get access thru my blocks they can handle all the functionality? right?

 

[Cowboy \(Gregory A. Beamer\) [MVP]]

The idea is the person running the block supplies the command (or
sproc/table name), type of command and all params and it returns the
DataSet, Reader, et al. I like the Microsoft Data Access App Block, myself,
as it is quite functional and supported by someone else. It takes a bit to
get used to, but it reduces code written in projects. There is one error in
the Block, in the Table names stuff. The line should be something like:

tableName = "Table" + i.ToString();

or something similar.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************
Think Outside the Box!
************************************************

Is anyone working with a data access blocks /layer to .NET Maybe I'm just

not getting it but how does it work. The way I understand the data access
layer/block is that they leave all the database functionallity out of the
database. Generice objects are setup for connections to the
database(Update, Read, Write, delete). With that being the case I would
have a generice access block for tables, views, stored procedures, roles,
rules and users. As long as the developers can get access thru my blocks
they can handle all the functionality? right?supports Post Alerts, Ratings, and Searching.