ACC97: IPF Adding DB with Large Number of Objects to VSS 4.0

 Last reviewed: June 5, 1997
Article ID: Q163349
The information in this article applies to:
  • Microsoft Access 97
  • Microsoft Visual SourceSafe, 16-bit and 32-bit, for Windows, versions 4.0, 4.0a

SYMPTOMS

Advanced: Requires expert coding, interoperability, and multi-user skills.

When you add a large number of objects to a Visual SourceSafe 4.x project, you may receive the following error message: 

  MSACCESS caused an invalid page fault in module SSSCC.DLL
This article assumes that you are familiar with using the client-side capabilities of Visual SourceSafe. For more information about Visual SourceSafe, please refer to the "Visual SourceSafe User's Guide" or Help topics available from the Visual SourceSafe Help menu.

RESOLUTION

Upgrade to Microsoft Visual SourceSafe version 5.0 or later, or reduce the number of objects in your database.

STATUS

This problem no longer occurs with Microsoft Visual SourceSafe version 5.0.

MORE INFORMATION

Steps to Reproduce Problem

WARNING: Following these steps will cause a general protection fault on your computer. Make sure you save and close any open work on your computer before following these steps.

  1. Create a new database with 1000 tables and 1000 queries.

  2. Add the database to SourceSafe 4.0. Note that you receive the page fault error message and that Microsoft Access quits.

Additional query words: ACCSCC VSS SCC source safe
Keywords : kberrmsg kbinterop ssacc ssint
Version : 97
Platform : WINDOWS
Hardware : X86
Issue type : kbprb

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: June 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.