Microsoft Access Backend

From database24
Revision as of 03:33, 28 February 2012 by Dec (talk | contribs) (Created page with "== General == It is good practice to separate put queries, forms, reports and the business logic into a frontend database and all tables into a backend database if not a dedicate...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

General

It is good practice to separate put queries, forms, reports and the business logic into a frontend database and all tables into a backend database if not a dedicated database server.

Architecture

Server

Every backend is a server no matter whether it is a Microsoft Jet or another type of database. Each server has a unique name.

Location

Development does not happen on the same machine all the time. The location is derived from the workstation name.

Environment

There are usually three environments, namely

  • Development
  • Testing / Pre-Production
  • Production

ConnectionType

Databases can be accessed through different types of connections like

  • Jet
  • ODBC
  • OLEDB

Model

The backend class has collections for each architectural aspect: <uml class style="scruffy" scale="75" direction="lr"> [Backend]1-*>[ConnectionTypes] [Backend]1-*>[Environments] [Backend]1-*>[Locations] [Backend]1-*>[Servers] </uml>

Retrieved from "http://wiki.database24.net/index.php?title=Microsoft_Access_Backend&oldid=369"