Sharing Violation Selecting Filename in Office Assistant

Last reviewed: March 24, 1997
Article ID: Q114413

1.00 WINDOWS kbother kberrmsg kbtool

The information in this article applies to:

Microsoft Office Assistant for Windows, version 1.0

SYMPTOMS

When you open a file by clicking the filename in the Microsoft Office Assistant, you receive the following error message if the file is already open:

   Sharing violation on drive C

Note that this behavior does not occur when you click on a Microsoft PowerPoint presentation (.PPT), or a Microsoft Excel template (.XLT) file. The problem only occurs when you click on a Microsoft Word document (.DOC) or template (.DOT), a Microsoft Excel workbook (.XLS) or a Microsoft Access database (.MDB) file when that file is already open.

CAUSE

This error message appears if either of the following is true:

You are using 32-Bit File Access in Microsoft Windows for Workgroups version 3.11
```
    -or-
```
You are loading the Share program SHARE.EXE in your AUTOEXEC.BAT file

WORKAROUNDS

To switch to a file included in the Microsoft Office Assistant, when the file is already open, do any of the following:

WORKAROUND 1

If you are using 32-Bit File Access in Microsoft Windows for Workgroups version 3.11, you can turn this option off with the following steps:

Run the Control Panel.
Choose the Enhanced icon.
Choose the Virtual Memory button, and then choose the Change button.
Clear the Use 32-Bit File Access check box, and choose OK.
Choose Yes to make changes to virtual-memory settings.
Choose Restart Computer so that the changes that you made will take effect.

Note that when you use this workaround, you may notice that some tasks on your system take longer than when you were using 32-Bit File Access.

WORKAROUND 2

In Microsoft Windows version 3.1, if you are loading the SHARE.EXE file in your AUTOEXEC.BAT file, and your system is capable of running Microsoft Windows in 386 Enhanced Mode, you can use an equivalent of the Share program, VSHARE.386. If you are running Windows 3.1, the file VSHARE.386 is included with the "VSHARE.386 for Windows" (WW1000) application note.

For additional information, please see the following article(s) in the Microsoft Knowledge Base:

   ARTICLE-ID: Q112025
   TITLE     : WW1000: VSHARE.386 for Windows

If you are running Windows for Workgroups 3.1 or 3.11 in 386 enhanced mode, you should already be using VSHARE.386.

WORKAROUND 3

To avoid receiving this error message without making the above changes to your system, do one of the following:

Use the Task List to switch to the application in which the file is open to access the file instead of clicking on the file name in the Microsoft Office Assistant.
-or-
Double-click the name of the file that you want to switch to in the Windows File Manager to activate the file that is already open. When you use this workaround with a Microsoft Access database, the database file is opened in a second instance of Microsoft Access.

Note that the error message does not prevent you from accessing the selected file. If you choose Cancel in the dialog box that contains the error message, the file that you clicked in the Microsoft Office Assistant is activated. Or, if the selected file is a Microsoft Word template, a new document based on this template is created.

REFERENCES

"Release Notes For Microsoft Office Assistant For Windows Version 1.00," (OAREADME.TXT)

KBCategory: kbother kberrmsg kbtool
KBSubcategory:
Additional reference words: 1.00 2.00 4.00 5.00 6.00 6.00a offasst
macppt winppt compound share err msg
Keywords : kberrmsg kbother kbtool
Version : 1.00
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" 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.

Last reviewed: March 24, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.