Have you gotten the bug fixes for Paradox 5 for Windows:
from CIS:
Bugs fixed in Pdoxwin 5.0, inline dated: 12/6/94
The Customized date format now works if the date separator contains more than 
one character. The error message is "Bad separator".
If the date format is Windows Long, and the country setting is Brazil in the 
control panel setting, you can now input any data.
report.print( reportPrintInfo ) now respects any printer settings in the 
report or that have been set using printerSetOptions, even if the report is 
open when the options are set.
There were a series of specific reports that would not print anything if 
there were 27 records in the table. Any more or less is fine, although it 
always warns about clipping.  This problem has now been corrected.
The Import Ascii Fixed length feature will now let you start at any other 
character besides the first character of each line.
4.5 correctly exported a fixed-length file in any order that the user 
specified.  In 5.0, if you re-arrange the field order the exported file would 
only contain data up to the field that deviates from the original table's 
field order.  This now works as 4.5 does.
Some insert queries appear to function properly, the inserted table indicates 
that x records were inserted, but only around x-n records were actually 
inserted.  The same query and tables works fine in 4.5.  This has now been 
fixed.  The numbers for x and for n varied upon system settings.
Printing reports with record dividers or a grid with other than a line type 
of double is approximately 5 times slower in 5.0 than 4.5.  This is now fixed 
and is as fast as 4.5 or faster.
Some Field labels did not word wrap in Reports.
Using dmUnlink(), dmRemoveTable(), dmAddTable(), and/or dmLinkToFields() used 
to cause a GPF but no longer does.
cMax on a number field in a tCursor no longer returns a string.  It now 
returns a number.
In a report, the group (of records) following a group that broke across a 
page no longer will display the calculated values from the previous group 
that broke across the page. The values that are printed will now belong to 
the group that they are associated with.
When using setRange() with a table variable, and using fields for the min and 
max values, if you do not specify the dot value part of (fieldname.value, 
fieldname.value) will no longer crash in PALRTL.DLL @ 0053:0663.
Doing a simple subtract where the table that has the subtractable fields is 
keyed in a least the first two fields will no longer cause a GPF in 
PXPALEXE.dll at 000D:03ED.
When attaching a TCursor to a detail table frame it now will respect the 
restricted view.  Previously, the restricted view was not respected and all 
records were displayed.
If a record band is set to less than twice the height of a field object, the 
text of last record on the page is no longer cut off.
Creating a dBASE table with the "LIKE" option now will create a table if the 
borrowing table field names have any extended characters.
On some reports, Text no longer will have very wide, random spacing between 
characters.
Using ExecuteQBE() to create :PRIV:ANSWER.DB and then using it again to query 
:PRIV:ANSWER.DB and specifying the answer as :PRIV:ANSWER.DB no longer 
results in an error when executing the second query.
Some reports no longer print incorrectly on a networked HP LJ III printers.  
The symptoms were: the report header used to be missing or in the wrong font 
on some pages; too few records per page were printed; etc. This has now been 
corrected.
===
 * QMPro 1.53 * With schizophrenia you're never alone!
--- TosScan 1.00
1:226/120)
---------------