What bugs in PB 6.5?

[Terry Black]

Please help. Our group is considering upgrading from 5.0.04 to 6.5 but
we keep seeing references to bugs in 6.5. Can anyone give me a brief
list of the known bugs in 6.5 so we can make an informed decision about
upgrading? Thanks in advance.

[Mark J. Johnson]

It is important to note (occasionally) that many developers are doing fine
with PB6.5. Ask yourself how many PB licences have been sold and compare
that to the number of bug postings. If 100 people say "PB is full of bugs"
that is still a tiny percentage. I absolutely don't want to imply PB is bug
free--I just think that, with the level of complexity in todays computing
environments, it works very well (no, I don't work for Sybase--just my
opinion).

Enough said.

Terry Black wrote in message <35EEC7D7...@hcia.com>...

[Lirvin Alexander]

Bug 1.
DW have a column decimal {4} flag and visible property = if
(flag=0.0001,0,1).
Some rows have flag=0.0001 and so they should not be visible. They are
visible.
If someone changes visible property to flag - 0.0001 bug disappears.

Bug 2.
On Windows NT when someone selects decimal (*,4) column into decimal {4}
variable from table of Microsoft SQL Server database and column's value is
for example 12312.2376 variable in 6.5 PBuilder will be 12312.2300. On Win95
etherythig is ok.

Bug3.

Let's imagine that You have a datawindow with one numeric field.
Edit style for that field is DropDownDW
(DataWindow="dw_ddw" ; Display Column="name" ; Data Column="id").
dw_ddw source is a set of rows from table like this :
{ id int not null, name char(30) not null}

It works fine while You are choosing a non-empty string value "name" in
dw_ddw, but If someone selects a (for example) { 12324, ' ' } row
PowerBuilder says :
"Item '' does not pass validation test."

Sincerly Yours.
Lirvin Alexander.

[martin....@alo.asgab.com]

One thing that is causing us problems is that the Incremental Rebuild does
not work. You have to make a Full Rebuild of your PBLs to be on the safe
side (to be sure to avoid compiler errors)
I think this problem occurs when the PBL you are doing Incremental Rebuild
on, has objects (that have been canged) with descendant objects in other
PBLs. PB fails to regenerate the object in correct order so you end up with
a lot of compiler errors.

Otherwise PB 6.5 works fine (large PFC based application run in a NT 4
environment against a Oracle 7.3 database). We jumped from 5.0.03 to 6.5

/Martin

[Manfred Jeschke]

Hi,

Here are my first impressions:
The resize service for OCX controls does not work. You can use the resize
service with parameters to scale and move the control. But for an OCX the
moving does not work.
I was not able to build an executable when I migrated from PB 5.0.04 to
6.5, using the old 5.0.04 PFC's. The build process ended in a GPF.
The editmask still does not work. Depending on the type (decimal, real) the
decimal values are cut off.

Greetings
Manfred

Terry Black schrieb:

[Georgios Papageorgiou]

Did you register this bug .

Sybase are looking for project which fails when you make incremental builds.

Please report it to sybase,

Georgios

martin....@alo.asgab.com wrote in message
<8Db4K81...@forums.powersoft.com>...

>One thing that is causing us problems is that the Incremental Rebuild does
>not work. You have to make a Full Rebuild of your PBLs to be on the safe
>side (to be sure to avoid compiler errors)
>I think this problem occurs when the PBL you are doing Incremental Rebuild
>on, has objects (that have been canged) with descendant objects in other
>PBLs. PB fails to regenerate the object in correct order so you end up with
>a lot of compiler errors.
>
>Otherwise PB 6.5 works fine (large PFC based application run in a NT 4
>environment against a Oracle 7.3 database). We jumped from 5.0.03 to 6.5
>
>/Martin
>
>
>
>Terry Black wrote in message <35EEC7D7...@hcia.com>...

[Oliver Sheen]

PB Bug 1.) Incremental Rebuild does not work in PB 6.5

PB Bug 2.) Sybase Adaptive Server Anywhere(SQL Anywhere 6.0) - PB does not
query for case sensitive table names in the database painter. this breaks
data manipulation painter because the table is not found in the database
when the query executes.

PB Bug 3.) Dynamic DataWindows with more than one table does not build
datawindow columns with the table_column naming convention. The table names
are also missing from the ".DBName" property.

PB Bug 4.) Must convert menu, window, and userobject structures into
standalone structure objects. For Full Rebuild and Project Build Executions
the compiler puts up a warning box for you to click "OK" at which point the
EXE and PBDs/DLLs start building. The Build waits for you to click on the
"OK" button. This feature eliminates the possibility of executing
unattended builds. Very costly and annoying.