Difference between revisions of "Microsoft Access Backend"
| Line 1: | Line 1: | ||
== General == | == General == | ||
| − | It is good practice to separate put queries, forms, reports and the business logic into a frontend database and | + | It is good practice to separate a frontend from a backend, |
| − | all tables into a backend database | + | ie to put queries, forms, reports and the business logic into a frontend database and |
| + | all tables into a backend database no matter what kind of database it is. | ||
== Architecture == | == Architecture == | ||
Revision as of 03:50, 28 February 2012
General
It is good practice to separate a frontend from a backend, ie to put queries, forms, reports and the business logic into a frontend database and all tables into a backend database no matter what kind of database it is.
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
Backend
Properties
The backend class has collections for each architectural aspect:
<uml class style="plain" scale="75" direction="lr"> [Backend]1-*>[ConnectionTypes] [Backend]1-*>[Environments] [Backend]1-*>[Locations] [Backend]1-*>[Servers] </uml>
It also knows all known connections as well as its tables and queries:
<uml class style="plain" scale="75" direction="lr"> [Backend]1-*>[Queries] [Backend]1-*>[Tables] [Backend]1-*>[Connections] </uml>