ACC2: Using SHARE.EXE and VSHARE.386 with Microsoft Access 2.0

ID: Q112125

The information in this article applies to:

SUMMARY

Moderate: Requires basic macro, coding, and interoperability skills.

Microsoft Access version 2.0 includes a version of VSHARE.386 that is compatible with Microsoft Windows 3.1, Windows 3.11, Windows for Workgroups 3.1, and Windows for Workgroups 3.11.

If you are using applications that support object linking and embedding (OLE) 2.0, you must run either SHARE.EXE or VSHARE.386. VSHARE.386 eliminates the need for SHARE.EXE when you run Windows 3.1 or Windows for Workgroups in 386 enhanced mode. If you run Windows 3.1 in standard mode, you still need to run SHARE.EXE.


MORE INFORMATION

Microsoft Access Setup will automatically install VSHARE.386 by copying VSHARE.386 into the WINDOWS\SYSTEM directory and adding this line to the [386Enh] section of the SYSTEM.INI file: 


   device=vshare.386

Setup will not automatically remove SHARE.EXE from the AUTOEXEC.BAT file, because it may still be required by MS-DOS applications running outside of Windows.

If SHARE.EXE is not required for any applications running in MS-DOS out- side of Windows, it can be removed from the AUTOEXEC.BAT file to free up approximate 5K of conventional memory. Leaving SHARE.EXE in the AUTOEXEC.BAT file will not cause any harm.

If Windows is run in standard mode then SHARE.EXE must be in the AUTOEXEC.BAT file. Add the following line to the AUTOEXEC.BAT file to install SHARE.EXE: 

   <path>\SHARE.EXE /L:500 /F:5100

In the example above, substitute the drive and directory where the SHARE.EXE file is located for <path>. For example, if the SHARE.EXE file is located in the DOS directory on drive C, add the following line to your AUTOEXEC.BAT file: 

   C:\DOS\SHARE.EXE /L:500 /F:5100

After adding SHARE.EXE to the AUTOEXEC.BAT file, restart the computer. 


Keywords          : kbenv 
Version           : 2.0
Platform          : WINDOWS 
Issue type        : kbinfo

Last Reviewed: April 2, 1999