MULTIPLE ACCESS DATABASE BACK-ENDS ON THE SERVER - VIRTUAL MULTIUSER

  • Thread starter Thread starter ljubo l via AccessMonster.com
  • Start date Start date
L

ljubo l via AccessMonster.com

I need an opinion about the following situation:

- There is a compay which has very good administered LAN (20 nodes) with
a very strong server.
There is a need within a company that 10 to 12 persons can
simultaniously access the server and run the
separate ACCESS acountiong software.When I say separate it means that
there wlill be up to 20 separate
ACCESS database data back-ends on the server.That means there are no
multi user problems because each
user work with a separate database.In fact, each of these databases
on the server represent one retail shop belonging to
the company. A chief accounting officer of the company can perform
an action "FORM The Company database"
which means that all the financial data from the separate databases
are collected and imported into the
central "Company" database .That will be done in the way that all the
crucial tables from the separate databases will
be linked to the central database.
Having in mind as follows:
- Each retail shop can be handled separatly
- None of the sepaate database will exced 500 MB and the
"Company database" will not exced 2 MB
- For the chief accountiong officer it is quite good to see
the "Company as the whole" once a day
(By actually forming the database by collecting the data
from the separate databases)
- No time to migrate to the SQL server

I think it is good solution BUT

I NEED THE OTHER PEOPLES OPINION about this solution!!
 
It'll probably work, but it seems very labor-intensive to me. Why not use a
single database, accompanied by a security scheme where each user that "logs
on" to the system only has access to their specific data? That way, one
database, and non-owners cannot see other data. As a matter of fact, you
could create a SQL database and link the tables to your Access front-end.
 
A single MDB file of 500 MB might cause you trouble because of the tendancy
of mdb files for "bloating". I don't know from where you got this number
but there is a clear possibility here of exceding the capacity of Access and
the fact that you want to link 12 of them for a total of 6 Gigs is
definitely asking for trouble.

Theoretically, this will work but in the reality, I don't know.
 
It think the system will work well. He can run procedures to place the data
from the different databases into common tables and running reports or form
views from them.
 
Back
Top