Another concideration: Is the database likely to change over time !
If you have 5 -similar- databases, and someone wants the result to be a bit
different, then you'd have to change 5 databases. Your choices now will
affect the cost of maintenance in the future.
In a similar setting I split the database in a front-end and a back-end, and
these were placed locally. After a change in the program, everyone gets a
new front-end, keeping the back end-local. In the back-end database I
inserted one table "settings" (with collumns "Setting" and "Value"), and I
created a user function GetSetting("<whatever>") that results in the value
of setting <whatever>.
In fact, there were three value-columns in my setting-table for different
cases where I needed a boolean, integer or string value.
For me this works fine, and all my users have the database tailored to their
needs when at the same time all reports and statistics can be gathered in a
general format.
Bas Hartkamp.
<po*******@gmail.comschreef in bericht
news:11**********************@p79g2000cwp.googlegr oups.com...
>I am working with several different departmnets on an accounting
database I created. It has been in use by one department for several
years to track reconciliations. Now several other departments have
expressed interest in tracking there reconciliations with this
database.
The dilemma:
All departments have requirements that are slightly different from the
other departments, but the output is the same; completed
reconciliations. Management requires one report that will display all
completed reconciliations along with details which will be unique to
each department.
The questions
Do I keep the same database and make modifications ?
How do I maximize speed when the database will sit on a server that may
not be the primary server for some departments. It seemed very slow
when I tried this
Can anyone reccomend a template for gathering the requirements ? I
have always used an informal template, but I am required to use
something a little more structured.
