Microsoft KB Archive/100461
PRACC9211: Cannot Overwrite Corrupt Paradox/dBASE Files
PSS ID Number: Q100461 Article last modified on 06-25-1993
1.00 1.10 WINDOWS
|The information in this article applies to:|
|- Microsoft Access versions 1.0 and 1.1|
Microsoft Access does not allow you to export a Paradox or dBASE table and overwrite an existing Paradox or dBASE file if the destination file has been corrupted. If you try to do this, the following error message appears: <path> This file already exists. Replace existing file? If you choose Yes, the following error message appears: Table ‘<tablename>’ already exists. This error occurs only with dBASE and Paradox files. Other database programs allow you to overwrite existing files when you export.
Microsoft Access attempts to open the file to verify, rather than to overwrite, its contents. Microsoft Access then reports the file as corrupted and returns the above error messages.
This behavior is by design.
Steps to Reproduce Problem
- Copy your CONFIG.SYS file to CONFIG.DB. (CONFIG.DB simulates a corrupt Paradox database.)
- Export any Microsoft Access table to Paradox 3.x.
- Specify CONFIG.DB as the output file and choose the OK button.
- When the “Replace existing file?” message appears, choose Yes. Result: The error message “Table ‘CONFIG#DB’ already exists” appears. Paradox is manufactured by Ansa Software, a Borland company, and dBASE is manufactured by Borland International, Inc., vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products’ performance or reliability.
Additional reference words: 1.00 1.10 import export KBCategory: KBSubcategory: IeaFx IeaPdox Copyright Microsoft Corporation 1993.