J
Joan
Hi,
I have built an mdb database and split the database so that the tables are
in the back end and the forms, reports, etc are in the front end. Using the
Jet database engine, what do I need to do now to make the database so that
it can support concurrent multiple users in a network environment? Am in
need of some good advice on how to proceed from here.
I have done some reading on Microsoft Access 2000 Client/Server Development
but read that access projects (.adp) require using either Microsoft SQL
Server 7.0 or MSDE (Microsoft Data Engine) and using MSDE requires a faster
processor, more memory, and is optimized for only five users whereas Jet is
generally best for no more than 25 to 50 users if they will be frequently
adding and updating data. At this time, SQL Server is not a consideration
because of the expense. The way that I understand it, the mdb format and
using the Jet database engine is more like a file/server solution and has
inherrent drawbacks with regard to reliability and additional network
traffic. I've also read that replication would not be a good idea if you
always need your data to be up to the minute current which I do.
There will be a minimum of 5 users in the business environment for which I
have built this database with the probability that this number will grow if
they extend the capability for salesmen to log on to check inventory amounts
and record sales.
Am thinking that for now, I should just go with the file/server option
using the Jet database engine but am not sure what exactly I should do to
make this work optimally. Any advice will be very appreciated.
Joan
I have built an mdb database and split the database so that the tables are
in the back end and the forms, reports, etc are in the front end. Using the
Jet database engine, what do I need to do now to make the database so that
it can support concurrent multiple users in a network environment? Am in
need of some good advice on how to proceed from here.
I have done some reading on Microsoft Access 2000 Client/Server Development
but read that access projects (.adp) require using either Microsoft SQL
Server 7.0 or MSDE (Microsoft Data Engine) and using MSDE requires a faster
processor, more memory, and is optimized for only five users whereas Jet is
generally best for no more than 25 to 50 users if they will be frequently
adding and updating data. At this time, SQL Server is not a consideration
because of the expense. The way that I understand it, the mdb format and
using the Jet database engine is more like a file/server solution and has
inherrent drawbacks with regard to reliability and additional network
traffic. I've also read that replication would not be a good idea if you
always need your data to be up to the minute current which I do.
There will be a minimum of 5 users in the business environment for which I
have built this database with the probability that this number will grow if
they extend the capability for salesmen to log on to check inventory amounts
and record sales.
Am thinking that for now, I should just go with the file/server option
using the Jet database engine but am not sure what exactly I should do to
make this work optimally. Any advice will be very appreciated.
Joan