Intro to the Site Maintenance project
Warning: This post is outdated. It is here for reference purposes only.
I've written before about an automated website backup and restoration tool, but I've left the overall picture rather vague so far. This post will start to remedy that problem. I've decided to call the project "Site Maintenance" but I'm not very good at naming things, so I apologize for its blandness. This post will go over the main features of the project from a "why would I want it?" point of view. Let's get started...
Creating a Web Interface for SQL Server Powered Application
This post covers how to get an ASP.NET Web Application to connect to the DEMO SQL database we created here. This is not a full tutorial on creating Web Applications, but instead focuses on how to connect the project to a database.
If you have already followed that mini-series, you ended up with an MS Access database as a UI. This post assumes you've followed at least the first post and have created the database DEMO with the three tables, two views, and one stored procedure.
Connecting SQL and MS Access - Part 3
So far in this series we created a basic database in SQL Server 2012 Express with a few tables, views and a stored procedure. Then in the second part we created the shell of our MS Access front-end, created a DSN file and connected two views on the SQL Server to Access. In this third (and final!) post of the series we will create a form in MS Access that allows a user to create a new person record and assign them to a department using the stored procedure we developed in the first post. As with the prior posts, I'm assuming a level of familiarity with the systems being discussed, such as SQL Server and MS Access.
Connecting SQL and MS Access - Part 2
In Part 1 of "Connecting SQL and MS Access" we created a basic database in SQL Server with three tables, two views and one stored procedure. In this post we're going to create a MS Access front-end database and link it to the views we created. We won't link to the base tables because we want all data access filtered through the views and stored procedures. If you are using a version other than Access 2007 or 2010 your steps may vary.
Connecting SQL and MS Access - Part 1
In my previous post, Building Reliable Data Solutions, I gave a 20-mile high view of how I use SQL and MS Access to collect and provide data to end users. What I didn't do was get into any of the nitty-gritty details of connecting Access and SQL Server together effectively, so this mini-series will attempt to cover those details. By the end of the series you should be armed with the basic steps I follow when creating a database driven system for others. In order to keep this a reasonable length I must make some assumptions about prior knowledge and experience as well as keeping examples somewhat simplified. If you feel like I have skipped something please leave a comment and I will try to address it!
In this post we will create a database using SQL Server 2012 Express edition. This database will be the foundation for the MS Access front-end we will create in future posts in this series.
Mastodon