Microsoft KB Archive/92674

{|
 * width="100%"|

PRB: TransferDatabase Macro Accepts Invalid File Names
'Article ID: Q92674

Creation Date: 12-NOV-1992

Revision Date: 19-SEP-1996' The information in this article applies to:


 * Microsoft Access versions 1.0, 1.1

SYMPTOMS

When you use the TransferDatabase macro action to export a database, Microsoft Access enables you to enter file names that include spaces in the Destination argument. Once the database is exported with a file name that includes a space, Microsoft Access will not be able to import that file. If you try to import the file, you may receive the following error message:

The filename is not valid RESOLUTION

If you export a file with a blank embedded in the file name, use File Manager or MD-DOS to rename the file without the space. This will enable Microsoft Access to import the file.

STATUS

This behavior no longer occurs in Microsoft Access version 2.0.

MORE INFORMATION

Steps to Reproduce Behavior

Create a table and call it Table1. Create the following new macro: Macro Name  Condition   Action -     Macro1                   TransferDatabase Macro1 Action -     TransferDatabase Arguments         Attribute Transfer Type:   Export Database Type:   Dbase or Paradox Database Name:   c:\access Object Type:     Table Source:          Table1 Destination:     Test Table Structure Only:  No Run the macro. This macro creates a file called Test Tab.xxx where xxx is the appropriate extension for the export type. Try to import this file. Note that you receive the following error message: Test Tab.xxx This filename is not valid


 * }

-

"THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED &quot;AS IS&quot; 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." '' ©1997 Microsoft Corporation. All rights reserved. Legal Notices.

''

Additional reference words: 1.00 1.10

KBCategory: kbinterop kberrmsg

KBSubcategory: IntpOthr