While all of that information is basically true, it neglects to mention that
a split database, rarely corrupts because nothing is shared except the data,
and that is locked by the user currently writing to that record or page.
While it alludes to network server connections being dropped as a cause for
corruption, it neglects to mention that tables without memo fields being
written to rarely corrupt, even with dropped connections. It also doesn't
mention that high quality networks, rarely drop a connection. Further, it
doesn't mention that transactional processing from unbound forms with
rollback will almost never have a problem either.
So databases designed by intelligent professionals, almost never suffer from
any of the problems mentioned. That said, if there is a mission critical
application that requires high security on a 24/7 basis, it makes sense to
spend the extra money for software, hardware, and administration to set up
and run a full SQL-Server application.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
message
In Microsoft's own words....
The following comes from Microsoft article Q300216.
-----------------------------------------------------------------------------------------------------------------------------------------------------------
"Microsoft Jet is a file-sharing database system. A file-sharing
database is one in which all the processing of the file
takes place at the client. When a file-sharing database, such as
Microsoft Jet, is used in a multiuser environment,
multiple client processes are using file read, write, and locking
operations on the same shared file across a network. If,
for any reason, a process cannot be completed, the file can be left in
an incomplete or a corrupted state. Two
examples of when a process may not be completed is when a client is
terminated unexpectedly or when a network
connection to a server is dropped.
Microsoft Jet is not intended to be used with high-stress, high-
concurrency, 24x7 server applications, such as Web,
commerce, transactional, and messaging servers. For these type of
applications, the best solution is to switch to a true
client/server-based database system such as Microsoft Data Engine
(MSDE) or Microsoft SQL Server. When you use
Microsoft Jet in high-stress applications such as Microsoft Internet
Information Server (IIS), customers have reported
database corruption, stability issues such as IIS crashing or locking
up, and also a sudden and persistent failure of the
driver to connect to a valid database that requires re-starting the
IIS service."
