Microsoft KB Archive/90985

{|
 * width="100%"|

PRB: Err with Wrong File Name Opening File That's Being Copied
'Article ID: Q90985

Creation Date: 26-OCT-1992

Revision Date: 19-SEP-1996' The information in this article applies to:


 * Microsoft Access versions 1.0, 1.1, 2.0

SYMPTOMS

Novice: Requires knowledge of the user interface on single-user computers.

On a computer with a shared drive, when a large database file is being copied to a new name or location and another computer attempts to open that database while the copy procedure is in process, an error message occurs stating that the database name (not the correct name for the database) is corrupted or is not a Microsoft Access database file.

Depending upon how the database file was opened, the following error message is displayed where &quot;Modules&quot; is not the correct name of the database file being opened:

NOTE: RO in the examples below means &quot;Read Only.&quot;

Opening Options            Error Message -  RO:  No Exclusive:  No  --> &quot;Database 'Modules' is corrupted&quot; RO: No Exclusive: Yes  --> &quot;Couldn't access file 'filename'&quot; RO: Yes Exclusive: No  --> &quot;Database 'Modules' is corrupted&quot; RO: Yes Exclusive: Yes --> &quot;Couldn't access file 'filename'&quot; CAUSE

Because of the way the operating system places file locking upon a file during the copy procedure, Microsoft Access has no way of knowing what is happening to the file being opened.

STATUS

This behavior no longer occurs in Microsoft Access for Windows 95 version 7.0.
 * }

-

"THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED &quot;AS IS&quot; WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY." '' ©1997 Microsoft Corporation. All rights reserved. Legal Notices.

''

Additional reference words: 1.00 1.10 2.00

KBCategory: kbusage kberrmsg

KBSubcategory: GnlBaddb