ACC95: Err "<Database> Isn't a Valid Name" Exporting Table/Query

Last reviewed: May 14, 1997
Article ID: Q160755
The information in this article applies to:
  • Microsoft Access 7.0

SYMPTOMS

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

When you export a table or query to a Microsoft Access, Microsoft Excel, Paradox, Text, dBASE, Microsoft FoxPro, or Lotus 1-2-3 file, you may receive the following error message and the export fails:

   '<DatabaseName>' isn't a valid name.

CAUSE

The name of your database file or the folder in which it resides contains a period (.) or an exclamation point (!) followed by one or more spaces, or your database file name does not contain a file extension. Following are examples of folder or file names that cause the error message:

   Path and File Name                    Reason for Error
   ----------------------------------------------------------------------
   C:\My. DotSpaceFolder\Northwind.mdb   Period plus space in folder name
   C:\MyFolder\My! BangSpaceFile.mdb     Exclamation plus space in file
                                         name
   C:\Access\Northwind                   Missing file extension

RESOLUTION

Rename the database file or the folder to a new name that does not contain a period or an exclamation point followed by spaces, or add an extension to the database file name.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access 7.0. This problem no longer occurs in Microsoft Access 97.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Copy the sample database Northwind.mdb to "My. DotSpaceFile.mdb" (without the quotation marks).

  2. Start Microsoft Access and open My. DotSpaceFile.mdb.

  3. Select the Shippers table in the Database window.

  4. On the File menu, click Save As/Export.

  5. In the Save As dialog box, click "To an external File or Database," and then click OK.

  6. In the "Save Table 'Shippers' In" dialog box, select Microsoft Excel in the Save As Type box, and then click Export. Note that you receive the error message.

The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.


Keywords : IsmProb kb3rdparty kberrmsg
Version : 7.0
Platform : WINDOWS
Hardware : X86
Issue type : kbbug
Resolution Type : kbfix


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