PRB: Fields Widths too Small on Transported dBASE Screen

Last reviewed: June 28, 1995
Article ID: Q124673
The information in this article applies to:
  • Microsoft FoxPro for Windows, version 2.6a

SYMPTOMS

Some field widths are too small (truncated) on screens transported from dBASE IV.

CAUSE

Transporting from MS-DOS to Windows poses a difficult issue of how to map monospaced fonts to proportional fonts. There is no algorithm to do this correctly in all cases. The Transporter does the best it can, mapping the monospaced fonts into units of average character width in the proportional font the user selects. This mapping ordinarily gives pretty good results; however the proportional field will sometimes be too long and sometimes too short.

WORKAROUND

Choose one of the following two possible workarounds:

  • Add a picture clause for the desired length of the field.

    -or-

  • Stretch the field so that it will accommodate the data.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce Behavior

  1. From the file menu choose Catalog Manager.

  2. In the open dialog, choose the samples subdirectory in the dBASE subdirectory.

  3. Open the samples catalog.

  4. Select the screens tab.

  5. Run the addbook screen.

Notice that the state field is not wide enough to display the state abbreviations.


Additional reference words: FoxWin 2.60a
KBCategory: kb3rdparty kbprb
KBSubcategory: FxinteropDbase


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