a Valid Bookmark
This message comes up
because at some stage your network connection has failed and records
may have become corrupted.
The information below
is taken from Microsoft Support Site page:
http://support.microsoft.com/?kbid=109730 Microsoft have removed the page from this link so
this link is no longer valid.
We would remind you to
regularly maintain your network and your computer systems to ensure
that your network continues to function. Please do not try to
link to a network via a wireless connection as they are inherently
unstable and are likely to cause data corruption to a linked database.
Problems May Cause "Segment Load Failure" Error, "System Process - Lost
Delayed Write Error" Error or "Invalid Bookmark" Error
Article ID: 109730
This article was previously published under Q109730
Moderate: Requires basic macro,
coding, and interoperability skills.
You receive a "Segment Load Failure" error message or another memory-
conflict error message.
In Microsoft Access 97, you may also receive a "System Process - Lost
Delayed Write Error" or an Invalid Bookmark Error message when viewing
data from linked tables.
A "Segment Load Failure" error message can occur if Microsoft Access is
running on a network or is accessing data on a network, and the network
server stops functioning correctly.
A segment load failure implies that there was a problem moving
information from secondary storage, such as a network server disk, to
main memory. If a network server stops functioning correctly, expected
information may not be available to Microsoft Access.
A "System Process - Lost Delayed Write Error" error message implies
that Microsoft Access had a problem writing data from its buffers to
secondary storage. This can occur if the connection to a Network share
stops functioning correctly. An "Invalid bookmark" error message will
also occur numerous times for each field on each record in the current
table or query that you are viewing if the share on which your data is
stored becomes unavailable.
The following suggestions may help you to diagnose the problem:
- Make a backup of all critical data and run disk diagnostic
software, such as the MS-DOS CHKDSK command, to check the integrity of
the workstation and server disk drives.
- If the workstation has a complete Microsoft Access
installation, quit and then restart Microsoft Access on the
workstation, and see if it operates correctly without using the network
for any services. If the problem continues with Microsoft Access
operating in isolation, begin checking the workstation for memory
- If the database is being accessed off a network server,
consider copying it to the local workstation to isolate whether the
problem is workstation or server specific.
- If the server is required, just start the server and the
Microsoft Access workstation to test Microsoft Access. If the problem
does not occur at this point, you can start and diagnose other
workstations one by one.
Article ID: 109730 -
Last Review: January 18, 2007 - Revision: 2.1
- Microsoft Access 1.0 Standard Edition
- Microsoft Access 1.1 Standard Edition
- Microsoft Access 2.0 Standard Edition
- Microsoft Access 95 Standard Edition
- Microsoft Access 97 Standard Edition
© Copyright 2020 - T. Bookman Limited
Company no. 04389244
in England and Wales
Go to Top