ACC97: Err Msg: "Could not create a valid file name" in VSS

Last reviewed: April 28, 1997
Article ID: Q162929
The information in this article applies to:
  • Microsoft Access 97

SYMPTOMS

Advanced: Requires expert coding, interoperability, and multiuser skills.

When you add an object to Visual Source Safe, you may receive the following error message:

   Could not create a valid file name for '<object>'. You must rename
   it before you can add it to Source Code Control.

CAUSE

You used a character that is invalid for Visual Source Safe in the object name.

RESOLUTION

Do not use any of the following characters in object names that will be included in a project in Visual Source Safe: "&", "@", "<", ">", "{", "}", "[", "]", "(", ")", ":", ";", "=", "^", "|", "*", "\", "/", "%", "?", ",", "'", """ or tabs. Some names in Visual Source Safe cannot begin or end with spaces or tabs.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Create a new database named "ssTest" (without the quotation marks).

  2. Place this database under Source Safe Control by selecting SourceSafe on the Tools menu and clicking "Add Database to SourceSafe."

  3. Create a new module.

  4. Save the module as "**<modTest>**" (without the quotation marks) and close it.

  5. Note that you receive the error mentioned in the "Symptoms" section. Click OK.

  6. Change the name of the module to "modTest" (without the quotation marks).

  7. Add the module to Source Safe by selecting SourceSafe on the Tools menu and clicking "Add Objects to SourceSafe."

REFERENCES

For more information about naming limitations, search the Visual Source Safe Help Index for "Naming Conventions."


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