Difference between revisions of "Microsoft Access Backend"
(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...") |
|||
Line 28: | Line 28: | ||
== Model == | == Model == | ||
+ | |||
+ | === Backend === | ||
+ | |||
+ | ==== Properties ==== | ||
The backend class has collections for each architectural aspect: | The backend class has collections for each architectural aspect: | ||
− | <uml class style=" | + | |
+ | <uml class style="plain" scale="75" direction="lr"> | ||
[Backend]1-*>[ConnectionTypes] | [Backend]1-*>[ConnectionTypes] | ||
[Backend]1-*>[Environments] | [Backend]1-*>[Environments] | ||
Line 35: | Line 40: | ||
[Backend]1-*>[Servers] | [Backend]1-*>[Servers] | ||
</uml> | </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> | ||
+ | |||
+ | ==== Methods ==== | ||
+ | ===== update ===== | ||
+ | ===== relink ===== | ||
+ | ===== amendConnections ===== | ||
+ | |||
+ | === Backend Connection === | ||
+ | |||
+ | === Backend Table === | ||
+ | |||
+ | === Backend Query === |
Revision as of 03:47, 28 February 2012
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
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>