It's now time to roll up our sleeves and get dirty with some code. Earlier versions of Visual Basic would employ a Standard Module to do the job. NET applications would most likely consist of a class module keeping in line with proper object-oriented coding conventions.
You will also be placing a control layer between your application and the database allowing you to ensure that all data is properly 'cleansed'. You will have the ability to modify your underlying database technology (moving from MS Access to SQL Server for instance) without affecting your application in a major way. There are two main advantages to using a data tier to access your database. This class module would act as the glue between the database and the application. The main purpose of the Database Tier is to provide a gateway to the database via a class module. This article will describe in detail one implementation of a Database Tier for Visual Basic.NET. Part two will demonstrate how to utilize the stored procedures created in part one by assembling a Database Tier that can be modelled and used in your own applications.
Part one described in detail how to create stored procedures in Access using ADO.NET and Visual Basic.NET. Welcome to part two of Access Stored Procedures.
