Paradox 4.5 bug fix 
Author Message
 Paradox 4.5 bug fix

I found this on CompuServe...this doesn't seem yo be available for
download.  It said several times to call 1-800-331-0877 for
information or to order.

FIXLIS.ASC

Customers have made us aware of these issues that they were running
into with Paradox for Windows 4.5.  In an effort to remedy these
problems, we have released an inline for Paradox that fixes the following
the problems.  The inline contains no additional features only the
following changes.

- When using BORLAND.FT style sheet, edit regions
  attached to a memo field with Complete Display set,
  always showed up gray at runtime regardless of what
  color is set.

- A new Sybase alias created from within Paradox did
  not have a datemode.

- Export Short Number field containing negative values
  to Excel format and negative values were interpreted as
  positive numbers greater than 32,000.

- In the data model dialog, begin defining a link to a Paradox
  child table that has 13 fields in its primary key.  Double-
  click on the child's index name in the Define Link dialog.
  Paradox failed in PXFORM.DLL.

- Paradox failed if you select Properties | Alternate Editor
  when a library window is open.

- When opening a 1 to many form linked to SQL
  tables without connecting to the server through the
  alias manager first, a crash in PXFORM.DLL occurred.

- File|Open|Report failed to use active DOS/Windows file
  system rules with code page 850 environment
  (international version).

- Form or Report based on dBase files, linked on a N1 field,
  would fail when toggle from run mode to design mode.

- If a large number of fonts are installed on the system and
  the printer setup is changed from inside of Paradox, the
  program would crash.

- Unique Aggregators in various reports did not give accurate
  results in all cases.

- After restructuring or sorting to the same table to the
  same name that has a .FAM file (created in version
  1.0), the original table was deleted. This only happened
  on a local drive only and not on a network.

- Dialogs and msgInfo's shown during open of form did not
  repaint the screen correctly.

- Calculations placed in header of GROUPS and in header
  of REPORT failed completely when group bands were in
  the report.

Newsgroups: comp.os.databases.paradox
Subject: [WIN] 4.5 Bug Fix!
Summary:
Followup-To:
Distribution:
Organization: The Ohio State University
Keywords:

I found this on CompuServe...this doesn't seem yo be available for
download.  It said several times to call 1-800-331-0877 for
information or to order.

FIXLIS.ASC

Customers have made us aware of these issues that they were running
into with Paradox for Windows 4.5.  In an effort to remedy these
problems, we have released an inline for Paradox that fixes the following
the problems.  The inline contains no additional features only the
following changes.

- When using BORLAND.FT style sheet, edit regions
  attached to a memo field with Complete Display set,
  always showed up gray at runtime regardless of what
  color is set.

- A new Sybase alias created from within Paradox did
  not have a datemode.

- Export Short Number field containing negative values
  to Excel format and negative values were interpreted as
  positive numbers greater than 32,000.

- In the data model dialog, begin defining a link to a Paradox
  child table that has 13 fields in its primary key.  Double-
  click on the child's index name in the Define Link dialog.
  Paradox failed in PXFORM.DLL.

- Paradox failed if you select Properties | Alternate Editor
  when a library window is open.

- When opening a 1 to many form linked to SQL
  tables without connecting to the server through the
  alias manager first, a crash in PXFORM.DLL occurred.

- File|Open|Report failed to use active DOS/Windows file
  system rules with code page 850 environment
  (international version).

- Form or Report based on dBase files, linked on a N1 field,
  would fail when toggle from run mode to design mode.

- If a large number of fonts are installed on the system and
  the printer setup is changed from inside of Paradox, the
  program would crash.

- Unique Aggregators in various reports did not give accurate
  results in all cases.

- After restructuring or sorting to the same table to the
  same name that has a .FAM file (created in version
  1.0), the original table was deleted. This only happened
  on a local drive only and not on a network.

- Dialogs and msgInfo's shown during open of form did not
  repaint the screen correctly.

- Calculations placed in header of GROUPS and in header
  of REPORT failed completely when group bands were in
  the report.

--

"Say, is that a UNIX book?"
       --Garth to Garthette



Sat, 24 Aug 1996 07:34:11 GMT
 
 [ 1 post ] 

 Relevant Pages 

1. 4.5 Bug Fix! (From CIS)

2. P4W 4.5 does not fix important bugs

3. Importing fixed length ASCII file into Paradox Win 4.5

4. Paradox [4.5,5.0][WIN] - Memory bug sol'n

5. BUG in Paradox 4.5 (DOS) New Triggers?

6. Bug in OPAL - Paradox for Windows 4.5 ??

7. Problems with Paradox 4.5 and WINDOWS NT 4.5

8. IMPORT PARADOX FOR DOS V 4.5 INTO PDOXWIN 4.5

9. GPF 11d4 at Paradox:68:02c4 Paradox DOS ver 4.5

10. Queries and reports from Paradox 4.5 to Paradox 9

11. Paradox 4.5 files with Paradox 9

12. Converting, Importing, or Updating Paradox 4.5 for DOS Scripts to Paradox 5 for Win


 
Powered by phpBB® Forum Software