V
Van T. Dinh
If your database is well-designed / implemented, and your
network hardware / software are good, that shouldn't be
any problem.
However, JET does NOT have a proper back-up / restore
procedure. Sometimes, corruptions do occur which takes
time to fix. Think this way: can you afford X numbers of
workers NOT working efficiently becasue the database is in-
operative for 1/2 a day or a full day. If you can't,
suggest you move up to a proper databaser server like MS-
SQL Server (NOT MSDE, the limited version of MS-SQL
Server) and use Access as the Front-End only.
HTH
Van T. Dinh
MVP (Access)
network hardware / software are good, that shouldn't be
any problem.
However, JET does NOT have a proper back-up / restore
procedure. Sometimes, corruptions do occur which takes
time to fix. Think this way: can you afford X numbers of
workers NOT working efficiently becasue the database is in-
operative for 1/2 a day or a full day. If you can't,
suggest you move up to a proper databaser server like MS-
SQL Server (NOT MSDE, the limited version of MS-SQL
Server) and use Access as the Front-End only.
HTH
Van T. Dinh
MVP (Access)