FIX: TRANSPRT.PRG Gives Wrong Message Converting dBASE Report

 Last reviewed: September 22, 1997
Article ID: Q122588
2.60 WINDOWS kbprg kbprint kbtool kb3rdparty kbfixlist kbbuglist

The information in this article applies to:

  • Microsoft FoxPro for Windows, version 2.6

SYMPTOMS

When you issue a REPORT FORM command using a dBASE IV report (FMT file) to PRINT, PREVIEW, or FILE, the TRANSPRT.PRG file first attempts to transport the file into a FoxPro format. Upon reaching 100%, the conversion is cancelled and a wait window appears that reads: 

   You must modify this dBASE IV file through the Catalog Manager.
Or when you try to use REPORT FORM with a DBASE III report, you receive an message from the Converter that reads: 

   Convert FoxBASE+ report file to FoxPro 2.5 format?
Both these error messages are incorrect.

RESOLUTION

The "You must modify this dBASE IV file through the Catalog Manager" messages is incomplete. To convert the file to an FRX, open the file from within Catalog Manager or choose Convert dBASE files from the RUN menu.

The "Convert FoxBASE+ report file to FoxPro 2.5 format?" message is incorrect because it is a dBASE III report file, not FoxBASE+.

STATUS

Microsoft has confirmed this to be a problem in FoxPro version 2.60 for Windows. This problem was corrected in FoxPro version 2.6a for Windows.

Additional reference words: FoxWin CatMan 2.60 wrong error buglist2.60
fixlist2.60a
KBCategory: kbprg kbprint kbtool kb3rdparty kbfixlist kbbuglist
KBSubcategory: FxinteropDbase
Solution 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: September 22, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.