-
Avoid the loss of power during
database writes. If power is lost during a database write,
that can cause the database to be left in a suspect state.
-
Avoid dropping network connections.
-
Avoid incorrect termination of
Microsoft Jet connections such as power loss, manual
shutdown, or allowing Task Manager to Shut down the
application.
-
Fatal system errors almost always
cause incorrect termination. If your database is prone to
fatal errors, you must resolve the errors before the
database becomes too damaged to open or to recover.
-
Compact the database frequently.
-
Do not run IPX on a windows NT- based
Server where Jet databases are located across the network
and the client is Microsoft Windows 95 with Internet Packet
Exchange/Sequenced Packet Exchange (IPX/SPX). Instead, run
TCP/IP on the Windows NT with IPX/SPX does not cause the
problem, nor does Novell to any Client).
-
Avoid a large number of Open/Close
Operations in a loop (40,000 successive open/close
operations to over 1,000,000).
-
Verify that the latest Microsoft Jet
Service Pack is installed on all client machines that access
the database file.
