4.5 Bug Fix! (From CIS) 
Author Message
 4.5 Bug Fix! (From CIS)

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 11:22:41 GMT
 4.5 Bug Fix! (From CIS)


: 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.

Assuming this is free, can someone who grabs it make it available via ftp?

Thanks
Brian



Sun, 25 Aug 1996 01:49:24 GMT
 4.5 Bug Fix! (From CIS)

: : 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.

: Assuming this is free, can someone who grabs it make it available via ftp?
Unfortunately, that's a bad assumption.  I just called, and they want $20.00
for it.  

: Thanks
: Brian
--
Larry Rose                                      Mission Research Corporation

(719) 528-8080 x(2062)                          Colorado Springs CO 80919



Mon, 26 Aug 1996 00:00:09 GMT
 4.5 Bug Fix! (From CIS)

 >
 > 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

If anyone has this, could they post it here or put it somewhere it can be
ftp-ed please? Rather hard to call 1-800 numbers from outside the US...

cheers,
peter

==============================================================================
             Peter Hyde, South Pacific Information Services Ltd
    Christchurch, New Zealand -- As close to Oz as the U.K. is to Albania

          (please use c.d.paradox for all relevant messages)



Wed, 28 Aug 1996 05:58:33 GMT
 4.5 Bug Fix! (From CIS)
Does anyone else feel that is unreasonable for Borland to expect us to pay for
bugs in their programs?  There is no justification for charging us for this.
If you buy a defective product, the consumer protection agency takes the stand
that it is the suppliers responsibility to correct the shortcoming, refund the
purchase price, or replace the defective item.  Why should software to excluded
from this?  How does Borland feel that they are above this?  And....  anyone
else interested in a class action law suit on this issue?


Thu, 29 Aug 1996 21:54:22 GMT
 4.5 Bug Fix! (From CIS)

: Does anyone else feel that is unreasonable for Borland to expect us to pay
 for
: bugs in their programs?  There is no justification for charging us for this.
: If you buy a defective product, the consumer protection agency takes the
stand
: that it is the suppliers responsibility to correct the shortcoming, refund
 the
: purchase price, or replace the defective item.  Why should software to
excluded
: from this?  How does Borland feel that they are above this?  And....  anyone
: else interested in a class action law suit on this issue?

I don't like bugs any more than you do and the less I have to pay for
something the better.

However, the big picture is how we, the users finance the development of
what we use. We can't legistlate quality. If we want a lot of new
features and buy a product that has a lot of new technology, there will
be bugs. If you don't want to live with that, you may want to stay with
older more proven products.

Personally if my client were to find a bug, or even if a part of a
program I wrote was a little confusing to the user, I would make it work
for them and apologize for the inconvenience, for free. But that is the
business I am in. I am not in business trying to match a feature list
from a competitor who also has a buggy product.

Anyway, I hope stuff we buy gets better, I hope they can do it as cheap
as possible, so we don't have to pay a lot. But the last thing we need is
to start to sue each other.

Wilhelm



Fri, 30 Aug 1996 04:21:03 GMT
 4.5 Bug Fix! (From CIS)

Well- I think it's like this:

There isn't a piece of software around, short of maybe a 1-2 line asm language proram, that hasn't got a bug in it. So would you rather have them deny that ther are any problems in all current releases, or would you rather that the company admits to them and publishes a timely release for which you pay shipping and handling on?

Otherwise, they'd just not tell you, and they'd release an inline release that fixes some things and wait for the next major release to fix most of eveything else.

--
Beavis kicks ASS! He KICKS 'em! Kicks, KICKS!  He rules, he RULES, RULES!!



Fri, 30 Aug 1996 07:07:13 GMT
 4.5 Bug Fix! (From CIS)
Actually, we can legislate quality and its is done in all industries every day.
As for the way that software development is funded, I'm not sure If you have
checked Borland's stock lately, but we are doing a fine job at funding what we
use.  Bottom line, the bug fix should be provided at an ftp site.  Its their
error, and for them to fix.  If they want to put a bit more in the initial
price of a package as a contingency, then that is perfectly acceptable.  Ford,
G.M. down to the local news paper all have to make corrections in a defective
product at no cost to the consumer.  I see no reason why software companies
should be excluded.


Fri, 30 Aug 1996 18:50:13 GMT
 4.5 Bug Fix! (From CIS)


|> Actually, we can legislate quality and its is done in all industries every day.
|> As for the way that software development is funded, I'm not sure If you have
|> checked Borland's stock lately, but we are doing a fine job at funding what we
|> use.  Bottom line, the bug fix should be provided at an ftp site.  Its their
|> error, and for them to fix.  If they want to put a bit more in the initial
|> price of a package as a contingency, then that is perfectly acceptable.  Ford,
|> G.M. down to the local news paper all have to make corrections in a defective
|> product at no cost to the consumer.  I see no reason why software companies
|> should be excluded.
   ^^^^^^^^^^^^^^^^^^^

Well, they are, and that's the way it is. Every single software package
that you buy (actually you are buying a license to use it, not the
software itself) comes with a rider that basically says
"This software is believed to be error free, purchase of this license
implies no warranty, if you open this package you are agreeing to this."
etc etc

Borland's stock price has nothing to do with this. There are a handful
of shareholders (about 4000) and millions and millions and millions of
user of borland products, from DBASE to Quattro to Paradox and C++.
If every user were to buy BORL stock, the stock would be at $500/ share
by now ;-)

when was the last time you got a refund on your "local paper" because
there were typos or some of the ink was smudged?

when was the last time you returned a car after discovering 3 months
later that the stick shift wasn't as smooth as in the showroom?

when was the last time you wore a pair of pants for a month and then
decided to return them because they made a noise when u walked?

get real.

Software, unless specifically created to meet a need that you specify,is
ALWAYS sold on an as-is basis. The 30-day money back return that most places
allow you, are more than fair, IMHO to quickly bring to surface problems that
you thought would not exist.

In agreeing with previous posters on this subject, there is no software
which is bug-free. There is nothing in NATURE that is bug-free. Even
protons decay after 10^31 years.  ;-)

So the m{*filter*}is "pay upfront or pay later". I prefer pay later, and
BORLAND agrees with me, as do millions of other users.

ps: the IRS likes "pay upfront though.." ;-)

-rg



Sun, 01 Sep 1996 00:50:38 GMT
 
 [ 9 post ] 

 Relevant Pages 

1. P4W 4.5 does not fix important bugs

2. Paradox 4.5 bug fix

3. Pdox 4.5 DOS round() errors and one fix

4. Importing fixed length ASCII file into Paradox Win 4.5

5. [4.5] Vertical Scroll Bar with Fix object

6. Need patch for bug fix for bug#56085 ref:Q244548

7. fix for BUG#599 & BUG 606

8. Crystal Reports 4.5 BUG

9. Forms 4.5 Bug ?

10. Bug in Forms 4.5 ?

11. TO_DATE in Forms 4.5: Y2K Bug

12. Printer-switching bug in pdoxwin 4.5


 
Powered by phpBB® Forum Software