Sybase数据库技术，数据库恢复专家

This has been reported previously in Case 40385070 in PB 4.0 and was tested in PB 5.0.04 build 18 with a different sample and was reported to work there. With this current sample I was unable to get RowsWritten to reflect correct value in any version of PB 5.0, 6.0 or 7.0.

I have reproduced this against build 4021 of PB 7.0

I also found the following additional problems while testing the above problem.

- When the tab UO is initially created, there is no initial tab page, unlike in PB 6.x. So after you have saved it and re-opened it, you can add controls onto the UO. If you add a command button onto the UO, you will get an application error: "The instruction at 0x111f405b" referenced memory at "0x00000018". The memory could not be "read"".

- After you have manually inserted a tab page onto the user object. If you place a tab control onto the tab page. You cannot alter it's position by using the mouse. There is also no position property for the tab control, so you cannot alter these values manually.

- After you have manually inserted a tab page onto the user object. You can place a control onto the tab object instead of the tab page (which is not allowed in PB 6.x). If you placed a static text control onto the tab object, you cannot see it or alters its properties, but you can select it from the control list. If you placed a command button onto the tab object, then you would get another application error: "The instruction at 0x111f405b" referenced memory at "0x00000018". The memory could not be "read"".

Per development: this is not a bug:
It is required for Jaguar components written in PB that use datastores. The reason is that the datastore allocates window handles which cannot be used in other threads. If you develop a component without datastores or the datastore doesn't need to maintain state across method calls then you don't need to bind the thread. The reason why we made it the default was to keep people safe because they could run into trouble if they didn't bind thread and tried to use a datastore and never know why.

Works ok on both platforms if autosize height is checked. Problem happens in header, detail,
summary and footer bands.

This functionality was lost due to a bug fix that properly escapes special characters in the data (like < & >) with < and >. Otherwise, these characters would corrupt the HTML that was generated. In order to regain this lost functionality, we added a new property that indicates that the value is HTML, (ValueIsHTML). This new property has been placed in 7.5 and cannot be back-patched because this would require a migration.

At minimum, the availability of some functions that would allow the trapping of the current object, scriptname and line number at runtime so that we can perform some basic exception processing in PB apps, PB COM objects deployed as OLE Servers and Jaguar components. Currently, SignalError() will trigger the Systemerror event in the app object and some code may be written to capture the object, script, line, and so on, but if you create a COM object from your NVO then this is not possible. Which leaves the choir of processing exceptions a difficult and often hard-coded type of task. It seems that this information must be somewhat available and a simple set of functions that could be called to return the current line number, scriptname and object would be greatly appreciated.

NOTE: Adaptive Server Enterprise v11.9.2 installed on Solaris does not experience this error.

Per Development: Third Party Problem.

From RE:
It is by design that PB7 only installs the runtime ASA files and not the full ASA product. It is a known/reported error in prior releases that PB installed dbengxx.exe instead of the runtime engine rt engxx.exe. So it is in fact a change in behavior to correct a problem from prior releases. If a customer wants the dbeng60.exe installed, they must also run the ASA product install.

Changes are reflected on a popmenu() when the changes are made to the instance of the menu prior to the popmenu().

The attributes tested were for visible and enabled.

On German keyboards the Shift key is also labeled UMSCHALT etc.
However in Switzerland the keys are labeled with the english expression,
i.e. SHIFT, CTRL, ALT, CAPS LOCK etc.

With German (Switzerland) regional settings, PB7 picks up the German settings,
this should be the English ones, for example SHIFT+F10 and not UMSCHALT+F10

Field is decimal(14,2) datatype in table definition and host variable in script is double datatype : in this case decimal precision is lost when fetching resultset. If host variable is decimal{2} datatype then all works fine.

Developer's comments:
=================
DW Painter is behaving as it was designed. The ModifyResultSet dialog is no longer. In its place is the columnspec view where, if external data source (or stored proc), the dbname (scroll to the right) is modifiable.

If you compare it to in the breakpoint tab and drag a break point, it shows a different mouse
cursor ONCE you're in the script panel.

PER DEVELOPMENT:
This is correct behavior, not a bug.

The problem was a variable set to "~142". This is fixed in 6.5.1 and 7.0 build 7010 and higher. (PBCMPxx.DLL) (this is fixed in a build in the EBF line and not in 7.0.1 build 6012 - the GA for 7.0.1 Maintenance)

Typical situation :
Master and detail window are shared with a datastore.
Rowfocuschanged event of the master is used to synchronize the display of the detail window.
Note : when deleting the currentrow the synchronization must be postponed, e.g. in a posted event.

Workaround
1) Resize control or datawindow height so that it will fit or enable the horizontal scrollbar
or use following scripts
2)
delete button ->
>>>
long ll_row

ll_row = dw_master.getrow() /* current row */
dw_master.setredraw(false)
dw_detail.setredraw(false) /* don 't update screen until your done */
dw_master.scrolltorow(1) /* workaround */
IB_deleting = true
ids_mystore.deleterow(ll_row)
ib_deleting = false
if ll_row > 2 then
ll_row = ll_row - 1
else /* 2, 1, 0 , -1 , NULL */
ll_row = 1
end if
dw_master.scrolltorow(ll_row)
dw_master.setredraw(true)
dw_detail.setredraw(true)
dw_master.setfocus()
<<<
dw_master rowfocuschanged ->
>>>
if not IB_deleting then dw_detail.scrolltorow(currentrow)
<<<

Per Development:
Not to be fixed.
The problem only occurs when the row height is larger than the datawindow height.
To work-around either the horizontal scrollbar can be enabled or the dw control height be increased.

[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'timestamp'.
No changes made to database.
UPDATE timestamp SET datachar10 = ? WHERE primarykeycol = ? AND tsequal(, 00000000100001783)

PB does not display the prefix '0x' when connected to the odbc driver. Under the native driver
it does display.

c:\--|
sybase (font text colour pink)
|-----------ase11 (font colour blue)
|----------- include (font colour red)
bin (font colour blue)
|---------- books (font colour red)
windows (font text colour pink)
|-------Cookies (font colour red)
|-------Config (font colour red)

Not a problem in PB 7.0.

1. Using right/left arrow will make the menu items disappear.
2. Can't close out of dropdown menu items
3. If you open more than 1 wysiwyg menu, the other wysiwyg menus don't
show the toolbar items
4. Selecting a dd menu item and scrolling thru the values of toolbaritemindex
and toolbaritemorder and then return to its original value will change/rearrange
the order of the toolbar icons.
5. The toolbar icons that show up in the wysiwyg menu and when you run the
app show different icons. If the toolbar icon shows a toolbarorder of zero, the icon
appears on the wysiwyg menu, but does not show up when running app.
6. Attaching a menu to a mdi window and than viewing the menu thru the wysiwyg menu,
changes the appearance.

Workaround: Make sure "visible" property changes made prior to "enabled" properties.

Per Development: Dup of CR186862 (inspect buffer buffer overrun fix) appleid to both pb65 and pb70 codelines.

The problem is when a datawindow which has a nested report is saved as file type 'PSR format', the edit style dropdowndatawindow saves the 'code' column instead of the 'display' column.

This problem occurs for a nested report which has a column object with edit style 'DropDownDW'.

The result is that for a nested report, the data column "code" (e.g. company_id) for the DDDW is saved instead of the "display" column(e.g. company_name).

However if the main datawindow is previewed in the datawindow painter or dataWindow print preview, this problem does not occur. DDDW correctly shows the "display" column(e.g. company_name).

Starting with PB 5.0.04, including all version of PB 6.X and 7.0 the application results in a Powerbuilder Application Execution Error (R0035) Error: Error calling external object function coomandbars at line ....... OLE Automation connecting to Word 8 using (word.application.8) in all versions of PB. Application is failing in a customer developed Macro that is trying to change the CommandBars.

Applies to PictureButton, PictureHyperlink, and Picture controls on a Window.

A Picture Button is based on the Button control and cannot assume a different background color.

For Picture Hyperlink and Picture Controls there is an Architectural limitation on PowerBuilders internal control structure.CR 273347 (enhancement request) has been created for resolving the architectural limitation.

For a workaround datawindow userobjects can be used to achieve a similar result. A short technical document is available on http://my.sybase.com/detail?id=1018236.

Works ok in pb 5.0.04 and win95.

If you click ok, pb creates a corrupted pbl.

PBhtgetform() is in PBnote60.dll. This is a protected and private function.

Lotus Notes DB does not appears to be corrupt as it works fine in Lotus Notes and only fails randomly from within PB.

When I attempt to run the app, I get: PB70 caused an invalid page fault in module PBVM70.DLL at 0137:1138c618.

PER DEVELOPMENT:
This seems to be Microsoft support DLL version specific:
COMCTL32.DLL - 4.72.3609.2000 - everything works fine
but
COMCTL32.DLL - 4.72.3611.1900 - we get "invalid property" on the control's property page but NO GPF.
My test case: PB7 bld 5019, NT4.0 SP4

My current theory is that the binary stream (the IPersistStorage) from the OLD version
of the control is incompatible with the NEW version of the control (which breaks the rules).
Everything works fine if the OLD control is deleted from the window and a NEW control is added.
Doesn't look like there's anything I can do when the control changes its binary data stream format.
WORKAROUND:
Delete the OLD control and add the new one.

CrossTabDialog() - Changing the order of the columns in the Values expression list will cause an Access Violation when you hit OK. Also happens in DW painter when previewing a crosstab dw and you click on the Design menu and click Crosstab... to get the same dialog window

PB 5.0.04 -> OK
PB 6.0.251 -> OK
PB 6.5.444 -> - (0xc0000005) 0x10b96cca
PB 6.5.555 -> - (0xc0000005) 0x1055f177

No workaround, fails from the dw painter in preview mode, using CrossTabDialog and also if using Modify()

Workaround: Use p-code or read into temp string variables prior to passing into function.

In pb 7.0, you need to click on the application object and than click on the object you want to open.
Its a two step process. In pb 6.0/6.5, it was a one step process.

Workaround:
You can do this after using the wizard by opening n_genapp_connectservice and modifying the function of_getconnectioninfo to have it point to wherever you want. The Wizard at this point is just meant to generate a typical situation.

Using odbc to connect to ms sql server. Using disablebind=1. Using
sqlsrv32.dll (version 3.60.0319). Works ok using ms native driver (though
using slightly different syntax.)

Getting error of:
Cursor is not open.

Used the following syntax:
DECLARE SP_DURATION PROCEDURE FOR dbo.pr_date_diff_prd
@var_date_1 = :ad_start,
@var_date_2 = :ad_end,
@rtn_diff_prd = :ls_duration
USING SQLCA;
Execute sp_duration;
FETCH SP_DURATION INTO :ad_start, :ad_end, :ls_duration;

Problems may arise with MIGRATED applications. You have to explicitly set the window icon on the frame window in MDI or on every sheet in an SDI application to "AppIcon!".

There were several performance problems related to this change (window open performance) as well. Migrated applications would have a blank window icon as "" and PowerBuilder would search down the PBD path for the "" icon (which it would never find). The performance bug associated with this change in behavior is CR204779 fixed in 7.01ebf build 7014.

windu_registryd4x -vers2 -prog xxxxxxxxx -d /tmp -k

In a grid datawindow the original column order is 1,2,3,4, if you move the columns by clicking and dragging to the following order 4,1,2,3. If you try and reset the column order to 1,2,3,4, with the following powerscript:

dw_20145523.Object.col1.X=is_col1
dw_20145523.Object.col2.X=is_col2
dw_20145523.Object.col3.X=is_col3
dw_20145523.Object.col4.X=is_col4

It does not work, the columns get ordered 2,3,4,1. If you run the same code again the column order gets set back to the original 1,2,3,4

1. Can't close out of dropdown menu items.

steps to reproduce:
on a window, add a sle.
With sle selected, go to Declare> User events, and add a new user event mapped to: pbm_settext
exit and save window.
From the library painter, right click on the window, Regenerate
=> get following compilation warning:
Library: d:\mypbl5\mywindow.pbl
Object: w_mywindow
sle_1 Class Declaration
(0002): Information C0148: The identifier 'text' conflicts with an existing property with this name. The new definition of 'text' will take precedence and the prior value will be ignored until this version of 'text' goes out of scope

Composite report with two reports where the second report has 'New Page on Group Break" checked. Neither report in the composite has 'Start on New Page' checked.

In PB 5.0.02 and 5.0.03 the first report in the composite displays then the first group from the second report is directly under the first report. The second group then starts on the next page.

In PB 5.0.04, 6.0, 6.5 through build 560 andPB 7.0 through build 5020 the first report in the composite displays and then the second report immediately breaks to the next page.

Workaround: Place composite report into another composite report and the report appears the same as in PB 5.0.02 and PB 5.0.03.

Fixed in 8.0 only.

- In reallity this can't work and compilator raises error "(0001): Error C0143: A readonly property may only be modified in an event or function in its parent class" when trying to compile such a line from a button put on the window.
- compilator raises error "(0001): Error C0143: A systemwrite property may only be modified in an event or function in its parent class" when trying to compile such a line from the window itself.
- Help should specify that it's a read-only attribute

"The import completed but not all methods could be imported.
See Jaguar Manager console for details."

The jagman.log file has the following entry:
AX Importer Warning: f_a was not imported.
com.sybase.jaguar.util.JException: Lookup failed for list of operations:
Component testing/PB70_uo_tjaguar_1 does not exist

The methods that do get imported into jaguar work ok when called from PB 7.0.

Application 1:

This application connects and disconnects from a 16 bit SQLAnywhere 5.5.x database.

Application 2:

This application just opens and closes a main window.

If app 1 is run on its own, the user can connect and disconnect as many times as he/she wants.
If app 2 is run alongside with app 1, the user can still connect and disconnect as many times as he/she wants.
If app 2 is stopped, if the user tries to connect with app 1, he will get the following GPF:

Application Error
PBSTB60 caused a General Protection Fault in Module PBODB60W.DLL at 000A : 09D5

Choose close. PBSTB60 will close.

I have reproduced the problem with build 560 of PowerBuilder 6.5, it also fails with all previous builds.

NOTE: The above scenario works on WIN 3.x and also with 32 bit deployed executables.

Per Development:
Not to be fixed.
There are no plans for Development to address 16-bit issues on 32-bit platforms. These types of issues, as stated in the Product Management Tech Doc below:

47860 PowerBuilder 6.5: 16-Bit Applications on 32-bit Platform
http://techinfo.sybase.com/css/techinfo.nsf/DocID/ID=47860

"Since the PowerBuilder development environment can produce applications for 16 or 32-bit native deployment on Microsoft Windows, the applications must be deployed to the corresponding Windows platform. 16-bit applications are only supported on Microsoft Windows 3.x."

Workaround Per Development:
The bug was a formula that was doubling of the space to the left of the nested report, during printing calculations, making the DW Engine think there were 2 horizontal pages.

So, a workaround in 6.5 would be to keep the nests against the left side of the primary report -- if information has to be indented, indent it within the nest.

I also noticed that the bug was exaggerated when the nested DWs had smaller units of measure than the primary DW. I had as many as 10 empty horizontal pages coming out. Therefore, a side-bar for 6.5 would be to make sure the nested DWs have the same units-of-measure as the primary DW.

Workaround: don't insert new rows in previewmode. You can switch between preview and non preview mode when you have to insert rows into a new dw without data like
dw_1.object.datawindow.print.preview = "no"
dw_1.insertrow()
dw_1.object.datawindow.print.preview = "yes"

Concurrency -> checked
Bind Thread -> unchecked
Pooling -> unchecked
Sharing -> checked

Linking object files for server failed! Error linking d:\xxxxxx See log file
d:\xxxxx\xxxx.log

If you close out pb, and recycle the jaguar server than go back into pb,
no problems. The execution of the project is ok.

W/A is to check the value and set to 0 if negative.

RESOLUTION:
Although the behavior changed between 5.04 and 6.0, this is not a bug. You should not issue a message box from a clicked event. The DW clicked event is issued from the buttondown part of the click, when the messagebox comes up, being modal it causes the edit control to have captured the mouse. Therefore, any subsequent click is routed to the edit control, no matter where the mouse pointer is.
The actual behavior change was in the runtime engine (PBVM) between 5.04 and 6.0. Dan further suggested that DWE ought to process the clicked event from the button up and this might prevent this condition. We may consider this in a future release but it would itself be a huge behavior change for DWE

Fax Document 42041 ="Determining the Row Number of the Row at the Top of the Page about to Print (PB 4.0, 5.0)". It does seem to imply that one can obtain the row number of the first row before the page is actively in memory, BUT this is not possible.
string lsFirstRowOnPage
lsFirstRowOnPage = this.Describe("DataWindow.FirstRowOnPage")
Using the above code does not find the First Row On the Page about to print but instead, it finds the First Row on the Page that is currently in memory.

Workaround: use parent instead of mdi frame name or better use the menuid to refer to menu.

Workaround:
Insert a dummy row into the datastore before you share the data. See Script

lds = CREATE datastore
lds.dataobject = dw_richtext.dataobject
lds.setTransObject(SQLCA)

//Workaround start
ll_rows = lds.Retrieve(1)
IF ll_rows = 0 Then lds.InsertRow(0)
// workaround end

lds.shareData(dw_richtext)

Workaround: Use column id syntax instead of the columnname syntax

WORKAROUND:
Create a global function (f_utp) that returns an integer and that has a integer parameter. The script for this function is :
return UnitsToPixels(ai_yParam, YUnitsToPixels!)

Then use your global function in your expression to return the y coordinates :
if( len(string(cf_1))>4,f_utp(10), if( len(string(cf_2))>4,f_utp(10), if( len(string(cf_3))>4,f_utp(10), if( len(string(cf_4))>4,f_utp(10), if( len(string(cf_5))>4,f_utp(10),f_utp(84))))))

The problem of this workarouond is that there's a problem when you print your datawindow...

function getstruct()
outer temp
// set integer fields of structure to 1
temp.field1 = 1
temp.embedded.field1 = 1
// return structure
return temp

Calling the function which cause the gpf.
integer embed_field
embed_field = getstruct().embedded.field1

Workaround:
outer embed_struct
integer embed_field
embed_struct = getstruct()
embed_field = embed_struct.embedded.field1

In 7.0, you modify the External Source datawindow through the Column Specifications view.
If the View is active, you will see Design/Data Source disabled in the menus. If the View is hidden, Design/Data Source will be active and clicking on it will bring up the Column Specifications view.

This is mentioned in the on-line books too.

In commandbutton_1 (cb_1):
I can type: this. and the list will display
I can type: parent. and the list will display
I can type: cb_2. but the list does not display
If I save the window, bring focus to cb_2 and then back to cb_1 and then type: cb_2. the list will display.

Add to the prompt-for-criteria dw functionality, so the developer can "pre-select" a value. This value would appear in the prompt-for dialog to the user. User could change this value or not depending on his permissions.

In 6.5, you could use '<HL>' in a computed field anywhere and get a horizontal line in SaveAs..(HTMLTable!) output but in 7.0 it escapes the greater than and less than signs with an ampersand. It has the same behavior for the HTML Datawindow output. This is a more generalized need to allow things like links or SRC tags in computed fields to be output "as is" as was the case in PB 6.5.

A new attribute for computed fields "ValueIsHTML" has been added to 8.0 to allow full support of this functionality. This is/will be available in 7.0.2 ebf too but only through Modify() of the attribute. This is so you won't require a migration.

Customers using 6.5 computed fields needing this functionality (with Web.PB or SaveAs(HTMLTable!) to move to 7.0 can make a few changes to their code and get this functionality back..

Steps to reproduce :
1. Connect to our sql anywhere psdemodb database
2. Create a new grid datawindow
3. Select employee table
4. Select emp_id, emp_fname columns
5. Go in design/unions menu to create a new union in graphics mode
6. Select employee table
7. Select emp_id, street columns
8. Click on return painter to validate the union => Get error message 'This union is not union compatible', but this union is compatible!!!

NB: If you go in syntax mode and you manually set the same query then it works

A nice enhancement to the autoscript feature would be to enable to programmer to choose how the selection list pops up. That is, should it execute via a pause... if so, after how long of a pause. May we always want it to show up immediately after we append the dot to a class name. Maybe we could use the new keyboard shortcut customization feature to invoke the popup list with a keyboard shortcut. I would prefer to press CTRL+DownArrow to invoke it myself.

RETURN CODE CHANGE actually returns a NULL not a 3 when the following conditions are present: No DataWindow object associated with DataWindow control or DataStore; new one assigned from DataWindow blob

USAGE SECTION CHANGE If the target of SetFullState does not have a DataWindow object associated with it, the blob will assign one. In this case, SetFullState has the effect of setting the DataObject property for the target.

Response from Development on this is as follows: We do not populate the dataobject property hence it returns a null, then the above mentioned script from help is incorrect that it gets assigned.

Solution: Checkbox columns are implicitly required so the FindRequired function is one way to handle this problem. You could also set
the initial value of the column.

Problem occurs when the component has the following properties:
1. Participating in a transaction
2. Times out (demarcation/deactivation is not checked)
3. There's code in the deactivate event that disconnects from a
connection cache.

Developers comments: This is not a bug, works as designed.

Product Support Engineering comments: Submit as a New Feature Request

PER DEVELOPMENT:
This was a conscious design decision because so much of the information displayed in the db painter is db driven. Instead of always retreiving data/information when an item is selected, users must explicitly choose to look at the properties by either double clicking or RMB and selecting properties. This would be painful against some remote servers such as DB2 that have thousands of objects. This will not be changed.

The expression for the computed field is 1.5*1.6.

Using
ls_syntax = LibraryExport("decimalpoint2.pbl", "d_test2",ExportDatawindow!)
dw_1.create(ls_syntax)

shows the dw in the dw control but the computed field is not evaluated or evaluated
incorrectly.

Problem is noticeable when the code examples is the selected/current
application.

Developer: There are two problems this causes:
To fix data retrieval problem, you must install SqliNet 9.20 or higher
To fix update problem, PBINxxx.DLL must be 6.5.1 (build 620)

We have a system that copes with mutli companies and each company has a
different way of keying in a certain code e.g.:

company 1 = ### ### ###
company 2 = #### ######
company 3 = ## ########

so if you had a expresion for the edit mask it would a whole lot easier to, at the moment its done with
allot of code in the rowfocuschanged event which is messy !

Customer has a lot of datawindows where a field is required dependent on another field value.
His workaround is he has to do a for loop before update to check for these. (time consuming
and annoying)

Customer quite often need to make a field required conditionally on whether they
have entered a certain value in a field on that row

DDDW with a string Null 'data column' with a corresponding display value, in this case the word "none". Problem is that the display value does not remain after tabbing off row. The user is allowed to select it but it does not remain in column. In PB 5.0 - 5.3 the corresponding display value of 'none' could be selected and would remain in place when user tabbed off column.

This worked in PB 5.0 - 5.0.3 but does not work in PB 5.0.4, PB 6.0,6.5 through build 575 or PB 7.0 build 5025.

Workaround: Put a blank space in rather than null and you can select and retain the value.

This seems to be a dw display problem because when the dw is saved to psr format, the columns are displayed correctly with no overlap.

WORKAROUND: Use disablebind=0 ( or do not explicitly set the dbparm. Disablebind is off by default.)

The following error message appears:
pb70.exe application error
The instruction at "0x112acf9d" referenced memory at "0x00000004". The
memory could not be "read". Click ok to terminate the application.

Customer feels they should be placed under a separate menu item such as Tools,
since looking under Window for them is not intuitive.

Have the ability to refresh the column specification panel when a change is made in the dw painter, without
closing it.

On nt:
PB70.exe Application Error
The instruction at "0x112bcdcb" referenced memory at "0x066c0f8e". The memory
could not be "read". Click ok to terminate the application.

On win95:
PB70 caused an invalid page fault in module pbvm70.dll at 0157:112bcd9b

pb70.exe Application Error
The instruction at "0x113b99e0" referenced at "0x00000065". The memory
could not be "read".
Click on OK to terminate the application.

Using ASE 6.0x and the EAS Demo DB.

The following error occurs:
pb70.exe - Application Error
The instruction at "0x1083ffd4d" referenced memory at "0x00000008". The
memory could not be "read". Click ok to terminate the application.

At design time opening a window is much slower in PB7 than in PB6.
Opening the window in runtime takes about as long in PB7 as in PB6

Much more information is required to be read in for the new window layout in the painter.

It seems that if the pbl is deleted, the items from the "to do list" should be removed/wiped out
too.

For example, if you click on a task that opens to a wizard to generate another object. New "To Do List" entries
are created. But you have to close the "To Do List" and reopen it to see the new task.

This works OK with all other English regional settings (Canada, Australia, South Africa etc)
The same problem exists with DM, FF, Pts (German Marks, French Francs, Spanish pesetas etc) using US English settings but not with the other English settings (except the above 3 Caribbean ones)

Simple Workaround: Prefix a '\' before the � sign - works with all regional settings.

The following error occurs before pb hangs:
Can't access this folder
Path is too long

When selecting an item from the dropdowndatawindow that has "Required" and "Empty String is Null" set, you will get a messagebox "Item 'null' does not pass validation test" regardless of which value is selected from the drop down list. With a dddw, there should be data in the buffer after the user has selected an item and you should never get this error.

The new 7.0 feature, DataWindow Stored Procedure Update, has a check box called "Use Original". When you setup the SPs for the Update, Insert and Delete tabs and check off the Use Original box for some of the arguments, you will notice that the check box changes are saved to different tabs when you view the DW SP update window again after saving it. This behavior differs based on the order in which you create the SPs. For example:

1) Going Left to Right (Update, Insert, Delete tab)

If you select a procedure for the Update tab and then check off the Use Original box for one of the arguments, then do the same for the Insert and Delete tab but check off the Use Original box for different arguments, you will notice that all the Use Original check boxes are set to whatever order was set in the LAST tab, in this case the Delete tab.

2) Going Right to Left (Delete, Insert, Update tab)

If you select a procedure for the Delete tab and then check off the Use Original box for one of the arguments, then do the same for the Insert and Update tab but check off the Use Original box for different arguments, you will notice that all the Use Original check boxes are set to whatever order was set in the MIDDLE tab, in this case the Insert tab.

3) Mixing up the orders (Insert, Delete, Update tab)

There is no consistent pattern as to what the check boxes are set to when you mix up the order of entering the procedures for each of the tabs. In any case, they are not set
correctly.

I have also noticed the Use Original check box disappearing and also unicode or garbage characters showing up in the Argument names for all the tabs but I have not been able to reproduce these behaviors.

In order for the computed expression to show, you must code in setredraw(true).
In pb 6.x, you didn't have to do this.

Enhancement - Changes to columns in a single table should be done as a UOW

"Unable to Read Registry Value: SOFTWARE\Powersoft\ObjectCycle\2.0.00\MSIDE\SCCServerName"

NOTE: The above error message is specific to ObjectCycle, but you can reproduce this against other 3rd party vendors.

If the user has administrative rights then this error message is not displayed. Also if you give "Full Control" to this registry key via REGEDT32, you will have no problems.

MSDAORA connect to Oracle 8.0 using the Net8.05 client:
Error: "Cannot create datawindow Microsoft OLE DB Provider for Oracle ORA-00900 invalid SQL statement" 1 execute system.CR169371_pss;0 RC1 = 0"
Note, when you select the sp, you will see a message stating "The database does not currently support retrieval of procedure text."
Also, this problems does not happen with the native O84 driver.

Intersolv Oracle 7 and Oracle 8 OLEDB connected to Oracle 7.x via SQLNet 2.3.x and Oracle 8.05 via Net8.05:
Because of CR192975, you cannot see the sps list when you are connected with the Oracle 7 provider.
Error: "Cannot create datawindow. SQLSTATE=37000 Intersolv Oracle8 OLEDB Provider [Intersolv][OLEDB Oracle8 Provider][Oracle8] ORA-00900:
Invalid SQL Statement"
Note, when you select the sp, you will see a message stating "The database does not currently support retrieval of procedure text."
Also, this problems does not happen with the native O84 driver.

Intersolv Informix 7 and Infomrix 9 OLEDB connected to Informix 7.x server via I-Connect 7.x and Informix 9.x servcer via I-Connect 9.16:
Error: "Cannot create datawindow. SQLSTATE=37000 Intersolv Informix7 OLEDB Provider [Intersolv][OLEDB Informix Provider][Informix] A syntax error has occurred.
Note this problem does not occur with the native IN7 and IN9 drivers.

If a retrieval argument is not used in a Select statement than a message pops up
saying:
"The (...) argument for the Select statement was not referenced. Do you wish to continue anyway?

The customer feels that this a popular way of passing data to a datawindow for sections not used
by the dw select.

The customer proposes the following message instead:
"The arguments were not referenced in the Select and are assumed to be datawindow arguments?

And in the datawindow, why not just call these "arguments" and not "retrieval arguments".

Threadpooling is a new option for the transport object for pb 6.5 and 7.0.

ThreadPooling: (valid values: 1 = on, 0 = off, default = 0 in pb6.5 and pb7.0)
Feature that was added to 6.5 to increase scalability. The basic
concept of this feature is that as a connection is completed, instead of destroying
OS process threads, they get pooled. It is faster to pull a thread out of a pool than
to destroy and recreate one via the OS. When a client is not processing anything,
the thread is available for other active users.

WORKAROUND: DisableBind =1

The method takes two arguments of:
ole_1.object.meth1("This is string1", "This is string2")

Pb will return the following:
This is string2
This is string2

Pb should be returning:
This is string1
This is string2

However, once you get this error message, you cannot get rid of it. If you try to retrieve from another table, you still get the same message. The only way to get rid of it is to disconnect and reconnect to the database

When previewing or running a crosstab datawindow and the user uses the mouse to drag the right side of a column to the left so that nothing in the column is visible and then drags the right side back out again the data will be visible, but the column header is missing.

The new controls are:
Progressbar
- HProgressBar
- VProgressBar
Static Hyperlink control
Picture Hyperlink control

For consistency and clarity, these new controls should have links to show a description
of properties/events/function the way treeview, listviews controls do.

The format is inconsistant to other controls.

Example is using "1998/25/12" which returns FALSE with IsDate() and '1900-01-01' with Date() which means "invalid" .
No good workaround with regional settings set this way.

Closely related to CR197884, 197886)

1) AutoSize Height for a column is ON
2) Line objects: Align Top or Bottom edges
3) Line objects Position property: SlideUp = AllAbove
If ANY of these three is NOT set, the page fault will not occur.
If all three ARE set but the Position property is set to DirectlyAbove the page fault DOES NOT occur.

*This does not happen in PowerBuilder 7.0.

Workarounds:
==========
#1. Don't ALIGN top or bottom edges using the menu option
#2. Set the Slide Up property of all fields of the two left-most Line Objects to "Directly Above" while leaving the Slide Up property of all other fields in the datawindow as "All Above".

Per Development:
Not to be fixed.

Running with both PB 6.5 and 7.0 resulted in the same page fault when run on a WIN95 machine.

IM7/PB7: no help for rtf replace option

eg a dw with 4 cols in select: dept_name, status, sex and salary (psdemodb)

Crosstab definition:

Rows: sex
status

Columns: dept_name

Values: sum(salary for crosstab)

Filter expression dw_1.SetFilter("status = 'A'") Shows the problem because the last row in this dw has a status of L (at least it does in my db) and this will get filtered out.

Status='L' works OK as do filter expressions Sex='M' and Sex='F'

This is fixed for post-7.0, and has been back-patched to 7.0 for the first EBF.

1. Add support for packages in addition to procedures and functions
in the painters. There is a system package now that properly
describes the functions/procedures within a package, so there is no
longer a reason not to include them.

2. Show sequences as another object type that PB can work with.

3. Use "CREATE OR REPLACE" rather than "CREATE" when
generating syntax for objects that support the "CREATE OR REPLACE"
option.

PWDialog currently allows the user to change an "expired" password.

Per Development, this is not a bug:
The problem is in the format mask itself. The compiler does not like the '-' after the [Red], it will only accept a '-' at the beginning of a section. A section begins just after the ';'. The following is a mask which will compile for English and German:
IF (figureunit = 2, '#,##0.00 %', '#,##0.00;-[Red]#,##0.00') Note the '-' is before the [Red] and directly after the ';'
The example is directly from the pbl and works for both German and English.

On solaris 2.5.1, the first printer in the box is always hightlighted after you hit the "save" cb.
On solaris 2.6, the second printer in the box is always hightlighted after you hit the "save" cb.

- having HTML Generation/Client formatting on for the datawindow.
- a datetime column (not just a date column)
- not the initial generation of the HTML, but the HTML resulting after a SetAction.

Tabbing OFF the column shows this data...

NaN/undefined/aN undefined:undefined:undefined

2) There is no search (&replace) across multiple PBLs.

SaveAs PSR format OK on Win98 (all versions)
SaveAs PSR format OK on NT (except low versions - PB5 crashes)

PB6.5 does not have a Deployment DLL kit for Finnish language.

PB Deployment Tested SaveAs WMF:
Win98 with French Deployment DLL's result PB65_444 Broken
Win98 with English Deployment DLL's result PB65_444 Broken

If you continue to connect/create shared object/destroy object and than
disconnect from the server, the thread count continues to incremate by 1.

dw_master.retrieve()
dw_master.sharedata(dw_detail)
dw_master.ResetUpdate()

WORKAROUND:
long ll_row
dw_master.retrieve()
dw_master.sharedata(dw_detail)
ll_row = dw_detail.getrow()
dw_master.ResetUpdate()
dw_detail.setrow(ll_row)

Tried the above workaround and setrow() did not work but ScrolltoRow() did.

Code sample that worked for me:
long ll_row

ll_row = dw_1.getrow()
dw_2.resetupdate()
dw_2.scrolltorow(ll_row)

If your source control system does not support Add Object function, then you are going to have to use the old method of performing version control. You'll have a set of registered libraries that everyone will check-in/check-out from and another set of libraries that people will test run their applications against to avoid the locking of the libraries.

So it sounds as though we'd have to:

1) change our lib list to include the registration pbl.
2) check out the object
3) change the lib list again to remove the registration pbl.

This is extremely inconvenient and difficult to work with.

Per development: This is believed to be a bug with IE 5. HTML DW works prior to IE 5 GA, and worked using IE 5 beta. Development
will attempt to code a workaround on our side, but can make no guarantee.

The line of code causing the performance problem is :

lds_merged.Object.format_code[ll_row] = lds_merged.getitemnumber(ll_row, "source_flag")

In the example that accompanies this case what used to take 2 seconds with pb5.0.04, now takes 2 minutes with pb6.5. If the line of code within the For loop is commented out, the performance is essentially the same as in PB 5.0.04. In this example the changes are being made to a datastore but when used with a dw it appeared essentially the same.

There were many CR's that appeared related, both still open and some fixed in 5.0.03/04. I did not find one that appeared to be exactly the same.

Resolution:
A couple of things needed to be changed (in the client pbl) to work properly.
1. Declaring a datasore as an instance variable rather than with in the event code and
2. Associating the datawindow control with a datawindow object

After the above changes, the dw control worked properly.

WORKAROUND:
implemt in clicked event something like:
long myrow
if dwo.name = 'datawindow' then
myrow = 0
else
myrow = row
end if

(dw_1.object.datawindow.HTMLtable.generateCSS = "no" or ls_rc = dw_1.Modify("datawindow.HTMLTable.GenerateCSS="no")

No is the default according to the documentation, but even if set explicitly it does not take effect in PB 6.5 for any style but grid.
With PB 7.0 it does not take effect for any style including grid.

When it is set to "no" the generated HTML should not include any reference to the classes generated in the "StyleSheet".

ResetUpdate() was fixed and does not cause RowFocus events to fire. However InsertRow() does. See below.

Per Development:
This is not a bug. RFC has to fire in the InsertRow() circumstance. All actions in the shared DataWindow environment take place on the parent DataWindow and the shared children are sync'd to the parent. The process of sync'ing to the parent sets the current row to 1 and current column to 1 and this will fire the RFC events. It is always necessary to sync to the parent and it is always necessary to set the current row and column.

6/25/99 Per Development this is not a PB bug:
The problem is that when doing a getremote function call for a cold link in service pack 4, the user is getting a return code from us of -3. In service pack 3, it returns cleanly. Even with a return code of -3, the data is coming back fine. In the code, after we've received the data we do a post of WM_DDE_TERMINATE and then we wait for our WM_DDE_TERMINATE. We never get the terminate and thus the -3. When I compare dde messages in Spy between service pack 3 and 4, indeed, we get our terminate in sp3 but not in sp4.

The following article describes problem with sp4 on nt 4.0 from Microsoft:
http://support.microsoft.com/support/kb/articles/q231/3/37.asp

You can create a project with a path that contains spaces/periods, but the build fails intermittently. If you move an existing project to a path which contains a space and/or a period/dot, you cannot change the properties to reflect the new path. You will get an error message of "Missing or Invalid Component Server File Name"

Workaround: Use directory names with no spaces or periods.

Problem occurred on both WIN95 and NT4.0 and when tested on NT 4.0 this did not appear to be related to any memory leak. Tried using Yield() and Setting redraw to false but this did not correct the problem.

You must manually entered it in. According to the Application Techniques manual
for PB 7.0, "Creating a service component", this property is automatically updated
for you when you deploy the service component.

The function declaration is as follows:
FUNCTION string getcwd(REF string buff, UnsignedInteger size) LIBRARY "/usr/lib/libc.x"

The function is being called as follows:
string ls_return, ls_directory
ls_directory = space(100)
ls_return = getcwd(ls_directory, 100)

Sun Solaris: On sun, the function works ok. Although if you take out the line ls_directory = space(100), pb will crash with a segmentation fault.
HP-UX: Calling this function above will just hang pb.
AIX: Calling this function will result in the following error:
Error opening DLL library xxxx/libc.a for external function at line 5 in clicked event of object cb_1 of w_test
Also ran as root and got the same error.

Application works ok using PB 6.5 solaris 2.6 (build 565).

Currently:
FUNCTION string getcwd(REF string buff, unsigned int size) LIBRARY "/usr/lib/libc.so"

Should Be:
FUNCTION string getcwd(REF string buff, UnsignedInteger size) LIBRARY "/usr/lib/libc.so"

In the Powerbuilder Powerscript Reference: Volume 1, Chapter 3, it discusses the datatypes
to be used for external functions. For unsigned int (32 bit platforms), it list UnsignedInteger.

Workaround: for example place in the resize event of the dw the values of the x and y propertie of the dw or move the dw back after the the setfullstate call by code.
example.:
this.x = 90
this.y = 200

See 200150 as well for memory leak fix related to setfullstate().

This works fine in 7.0 and in 6.5 builds > 1065.

In PB 6.5 the problem with the textcolor still exists but when running the window the entire backcolor is changed to the color selected.

Other information: The Treeview control uses the WindowText and WindowBackground for the font regardless of what is chosen. The background will be the font background but the the label (text) of the treeview items always uses the windowbackground text color. You can see this by importing the .srw and twiddling the NT defaults:

The treeview is taking on the Window Text color of the NT system. To see this.
- Right Mouse on NT Desktop
- Go to "Appearance" tab
- click on "Window Text" area to populate the Item/Font values.

For the items:

Item:

Font:

This is what controls the background of the treeview and the treeview icons (things like Folders). The user believes this should be controlled by the

treeview.fontcolor
treeview.backcolor

attributes instead of going directly to the NT defaults. (and ignoring any changes to these two treeview attributes.

Workaround: There is a DBParm that you can set in script or in the Profile in the Syntax tab under formats. Format DateTime to: =' \''mm-dd-yyyy hh:mm:ss.fff \'' ' so the time part will have 3 digits instead of 6.

Under nt 4.0 sp4, when closing out of Netscape 4.5, the browser will gpf.

On win95b, (KFrantz) used Netscape 4.06.

Workaround: Works ok on nt sp3 and win95a.

The example expression on the dw is as follows:

If (cmp_frame = 1.1, 'L', if (cmp_frame = 0.9, 'S', 'M'))

So entering a value of .9 for cmp_frame should have this expression
evaluate to 'S'. And it does, when regenerated from the Library Painter, or from an exe generated by the project painter. But
when the datawindow is regenerated with ORCA, or an executable is made through ORCA it does not evaluate
properly, returning 'M' instead.

The following expression which should be equivalent and always evalutates correctly:

If (cmp_frame = Dec ('1.1'), 'L', if (cmp_frame = Dec ('0.9'), 'S', 'M'))

If a full rebuild in the Library Painter is done after the ORCA regeneration then it also evaluates correctly. Although I could not test it because the ORCA sample only includes PB 5.0 functionality there is a possibility that if the PB 6.0 ORCA pborca_application rebuild was performed prior to building a runtime library or executable the resulting evaluation will be correct.

When viewing an export of an nvo from pb6.5 and 7.0, the exports look the same.
It doesn't appear that the functions are in their twice.

This was also a problem in PowerBuilder 6.5 but it now works okay with build 590 (NPDWE60.DLL)

execute sp_customer_list;

Workaround:
The following statement works ok:
exec sp_customer_list;

The above two statements both work in PB 6.x.

Quick repro:
1) Create an external datawindow
2) Name the first argument, tab to type (string) and either leave it string or change to decimal. Now tab again: goes to the next argument line, not to the length (for string) or dec (for decimal). You have to click or Shift-Tab to get back.

WORKAROUND:
Use a validation rule and move the code from the ItemChanged event to the ItemError event

Under certain circumstances if one modifies the color of the background on a DDDW while program is running it will cause the text in the first row to dissapear. This only happens if the DDDW has focus and the text reappears when you tab off the column. This also only happens the first time the column has focus.

When the sample is run on NT 4.0 it is impossible to open more than 12 sheets on my machine. If sheets are closed and then new ones are opened the limit is still 12 on my machine. If the menu is changes so that the sheet's menu has less items them more sheets are able to open.

When sample with large number of menu items was run on WIN95 in excess of 50 sheets were opened.

If the application just called the external function without connecting to
Informix than no problem. Using the native informix driver. Works ok
using informix thru odbc. Worked ok on win95b in PB 6.0. Works ok on nt 4.0.
Works ok in PB 7.0 (build 5031) on win95 and nt 4.0.
Failed in (builds 444 thru 585) on win95b. Failed in win95a in PB 6.0 and PB 6.5.

Per Development, this is not a PB bug, it is a Third Party problem. Customers can use the following workaround:
1) Declare the following local external functions:
FUNCTION ulong GetModuleHandleA(string dllname) LIBRARY "kernel32.dll"
FUNCTION boolean FreeLibrary(ulong hMod) LIBRARY "kernel32.dll"

2) Add the following logic PRIOR to disconnecting the transaction object for PBIN760:
ulong hMod
boolean bRC
hMod = GetModuleHandleA("TestDll.dll")
if IsNull(hMod) then
MessageBox("Error", "Unable to obtain handle for testdll.dll")
else
bRC = FreeLibrary(hMod)
end if
/* Now that TestDll has been freed, the atexit processing for isqlt07c will occur while pbin760 is still in the process address space */
disconnect using sqlca;

The data value for that column is 0000-01-01 00:00:00:000000 instead of NULL

Try to update the database with a datetime deleted from this editmask and the SQL generated is...

UPDATE tablename SET datetimecol = '0000-01-01 00:00:00.000000' WHERE ...etc

Up to 6.5.502 the SQL generated was...

UPDATE tablename SET datetimecol = NULL WHERE ...etc

The data is also correctly set to NULL if it's a date column instead of datetime or with other editmasks eg dd-mm-yyyy or even yyyy/mm/dd

Also happens with datetime editmask controls and GetData() -> gives 0000/01/01 00:00:00 and returns 1 (success)

Link Errors - Create of Executable file failed. If the Icon is removed the executable is created without a problem,

Works ok as a pcode exe and in development on nt/win95. Works ok on nt as a machine code
exe when using /pbdebug.

This causes a component to never get deactivated (assuming that autodemarcation is off and setcomplete is never called) and thus never destroyed.

WORKAROUND:
When the property (.timeout) is set manually from Jag manager, everything works properly.

Problem happens using Sybase Adaptive Server 6.01.

Works ok when tracing is not turned on. No crashes and output parm returns
result. No problems using rpc.

Additionally in PB 7.0 the same thing is happening on a Date field with the same editmask of mm/dd/yyyy. In all other versions of PB tested the Date field would see this as Null.

Works ok in pcode and in development.

The problem is in the of_detail_list function in the cvuo_lv_container.
Crashes in exe:
ll_row_count = lds_level1.Retrieve(ast_keys.location, ast_keys.work_id, &
ast_keys.hardware_id, ast_keys.hardware_type, ast_keys.cost_centre )

Works in exe:
ll_row_count = lds_level1.Retrieve(ast_keys.location, ast_keys.work_id, &
integer(ast_keys.hardware_id), ast_keys.hardware_type, ast_keys.cost_centre )

The properties that don't save are: Day, Month, Year under the general tab.

Properties that don't take effect when running app are all the properties under the
font tab.

Properties do change when scripted programmically.

Note: Same happens using the Desktop Toolkit 5.1 for ActiveX: Genesys TButton Control
ie. the objects properties like Font and Fontsize are not saved in development environment.

Problem: resize event
ole_1.width = this.width
ole_1.height = this.height

Workaround: resize event
ole_1.width = this.width - x
ole_1.height = this.height - x
(Where x can be 100, 200, etc.)

Using the workaround will fully resize the ocx so when you click on the ocx, nothing
happens--ocx will stay the same size.

Well, it turned out (forehead slap) that I hadn't set the update specs for the datawindow. (I'm not really using the datawindow for an update, I'm nly using it to generate a form I use to get retrieval arguments for the _next_ datawindow).

I guess that I had just expected different behavior (HTML form not generating, or something else) rather than a 'Reloading the current context failed' error message if I forgot to include the update specs....

I'm trying to add a SelfLink to the text items that are in the header of a grid datawindow. I set the self link to:

cgi-bin/pbcgi70.exe/port/user_object/method?argument=name_of_column

Because I want the web page to tell the user object which column header the user clicked on. What gets generated as the link for those text items though is:

cgi-bin/pbcgi70.exe/port/user_object/method?argument=name_of_columnname_of_static_text=static_text_text

That is, if the static text is called 'mycolumn_t' and the text on that static text is "MyColumn", the link that is generated has "mycolumn_t=MyColumn" stuck on the end of the link. Where is this coming from? How do I get rid of it?

What I tried before I tried this was to put a command button on the datawindow, tie it to the Sort event, and have the datawindow automatically generate the link based on that. According to the online help, Sort is one of the events that will result in a link. However, when I generate the HTML, there is no link for the Sort button.

This is not a serious problem because the sheet menus are disabled and do nothing, but it is a regression and could be confusing.

Must have all 3 steps to reproduce: SelectBlob -> Copy -> Paste -> Exit PB.

Per Development:
This issue cannot be addressed in PB6.x or PB7 or pb7ebf. T he resolution of this problem is being deffered to a major release.

PostUrl arg Server Port Result
"http://localhost:80/" 80 OK
"http://localhost:8080/" 80 OK
"http://localhost:8080/" 8080 KO
"http://localhost:80/" 8080 KO

Workaround: Use the filetype of Excel!.

Using the command "file <exename>" generates a response of data. The
correct response using this command on an exe should be:

ELF 32-bit MSB executable SPARC Version 1, dynamically linked not stripped

Works ok on solaris 2.6, hpux and ibm aix.

Using pb 6.5 (build 565) using windu 4.0 and 4.2.

Per Development this was a User Error:
Resolved by adding /usr/ccs/bin to the path statement.

PB fails using the MS SQL Server ODBC Driver 3.70.6.23
The error in PB is:
"A Database Error occured, Database Error code 999
Select error: SQLSTATE = 22005 [Microsoft][ODBC SQL Server Driver]Invalid character value for cast specification"

Two workarounds exist:
1) use version 3.70.08.20 and Disablebind =1
2) SELECT col1, col2 from mytable
WHERE convert(char(10), col1) = :arg1

Bypassed Objects:
The following objects contained circular references and were bypassed:
nv_format
nv_format_bso_a

This worked from 6.5 build 444 to build 530.

Workaround: check in all objects prior to migration.

Per Development:
Not a bug, but several documentation errors in example code.

Add the ability to "resize" the layout view to a proportion of actual size. For example: upon opening a window, the Layout view would show 100% of the window, even though actual size may be reduced to 75% in order to display it. A setting can control whether or not this should happen at load time. Standard proportions should include 50%, 75%, 100%, Window Size (or Best Fit) and Custom. All settings except for Best Fit would remain static between objects, while Best Fit would resize the object to fit the view.

dw_1.modify("Datawindow.crosstab.rows="' + ls_setting + '"")

The ls_setting is populated from:
dw_1.describe("Datawindow.Crosstab.rows")

The crosstab dw is defined with a symbolic notation at the end of the row.

Workaround:
In the dw painter, if you uncheck the "Rebuild columns at runtime", previewed the dw and
rechecked the option, app worked ok. This works unless you plan to use the column tag
property. If you do, the gpf or reference memory exception still happens.

This is not a bug and has been explained by engineering as follows:

This 'regression' is caused by a change of behavior intorduced in 5.0.4. Earlier the development behavior used to be different than the runtime behavior. An internal DBI call DBI_ADJUST_CONNECT was missing at runtime. When this behavior changed a lot of regressions were reported mainly due to the dependency on an unrecommended approach. The table names should be qualified with the user name if they are to be used by any user other than the owner...

Pipeline does not work unless you hardcode the DBO into the pipeline object.

This worked in PB 5.0.3 and appears to be the same or similar to CR163406. This may turn out to be an intentional change requiring a fully qualified table name as the destination. but as it worked as submitted in PB 5.0.03 it is being submitted as a regression.

Build tested for CR163406 are not available to test and next available builds (5.0.04 build 76 and PB 6.0 build 251) fail with this sample. In all versions tested the workaround stated in this CR worked.

WORKAROUND: Export the pipeline object and fully qualify the table name with the owner in the destination section. I was able to simply open up the pipeline and choose the correct table name and then the sample worked. What leads me to believe that this may be an intentional change is that when I tried to change the table name back to the original empty destination in the painter it would not allow me to change it back

Per Development:
Not to be fixed.
Workaround:
1. Create a User Event in which to perform the Modify
2. Post that event from within the ItemChanged event.

Add built in error handling such as On Error, or Try, Catch.

ISUG Enhancement Request e15_038.

Example for the select stamente:
WITH ERGEBNIS
(FA, SGR, SACHNR,SGRU,SACHNRU,MENPRZ,AUSBST,STUFE ) AS
( SELECT A.FA,A.SGR,A.SACHNR, A.SGRU,A.SACHNRU, A.MENPRZ,A.AUSBST,0
FROM AST40TAB A
UNION ALL
SELECT C.FA,C.SGR,C.SACHNR,C.SGRU,C.SACHNRU, R.MENPRZ * C.MENPRZ/100 ,C.AUSBST, R.STUFE+1
FROM ERGEBNIS R , AST40TAB C
WHERE R.FA=C.FA AND R.SGRU = C.SGR AND R.SACHNRU = C.SACHNR AND c.menprz > 1 AND R.menprz > 0.1 AND R.STUFE < 3
)
SELECT FA, SGR, SACHNR,SGRU,SACHNRU,MENPRZ,AUSBST,STUFE FROM ERGEBNIS

Workaround: Set PBSupportBindSelect = 'NO'

This works fine in development and in P-Code executables. If you try this in a machine code executable, you will get the following error message:

PowerBuilder Application Execution Error (R0005)
Application terminated.
Error: Negative value encountered in function

If you pass any other number to LogTen there is no problem.

The documentation states that if the treeview's editlabels property is enabled,
the user can edit an item label by clicking twice on the text.

Action: Load SaveAs file in PB6.5 dw plug-in using Netscape Communicator v4.51 browser.
Datatype Presentation Style Result
PSReport! Tabular PSR OK
PSReport! Rich Text PSR Not supported
HTMLTable! Rich Text HTML OK (Display data in the form of a table)

Dw_1.rowcount() does return the correct number of rows in the PSR file.

However the following functions do not work for scrolling the document instances on the Rich Text PSR file when the file has been loaded in the dw:
ScrollNextRow() Result returned = 0
ScrollNextPage() Result returned = 0
ScrollPriorRow() Result returned = 0
ScrollPriorPage() Result returned = 0

Property value for the following is incorrect whereas for a Tabular PSR, PB determines values correctly.
Integer(dw_1.describe("Datawindow.FirstRowOnPage")) Result returned = 0
Integer(dw_1.describe("Datawindow.LastRowOnPage")) Result returned = 0

PDF is a fairly common document format on
the internet. Because Adobe wants to promote the use
of that format, they allow for third-party products
to write that format.

% denotes document that is current after 10. Notice:

1. Word sorts it by name (if you opened Document11, it would be right after Document10)
2. Excel sorts it in Reverse order. 10,9,8,7...
3. Powerbuilder, with > 9 windows puts the last window opened or currently active window in position 9 at all times.

Word
1 Document1
% 2 Document10
3 Document2
4 Document3
5 Document4
6 Document5
7 Document6
8 Document7
9 Document8
...More Windows

Excel
% 1 Book10
2 Book9
3 Book8
4 Book7
5 Book6
6 Book5
7 Book4
8 Book3
9 Book2
More Windows...

Powerbuilder Genapp
1 Sheet:1
2 Sheet:2
3 Sheet:3
4 Sheet:4
5 Sheet:5
6 Sheet:6
7 Sheet:7
8 Sheet:8
% 9 Sheet:10
More windows...

Workaround: You must paste the mask from the clipboard in order to change it. IE bring up notepad and type in the editmask you want - copy and then paste it into the Powerbuilder datawindow dialog.

Developers comments: Deferred since PBSYT60 is not strategic and was never delivered for PB 7.0

Example:
Type in 00/00/2000 and then tab out
returns 01/01/2000

Type in 01/01/0000 and then tab out
returns 00/00/0000

In the edit control validation process, the above examples should fail
in the validation process triggering the itemerror event.

Workaround:
Edit the IDL module as follows:
#include <TabularResults.idl>
#include <CTS.idl> <-- add this line

As of May 20th, 1999 only version 1.4 of the JDBC driver is supported. You need to go to the Informix.com site (which redirects you to intraware.com to get either the 1.4 or the 2.0 driver). Support for 2.0 should be added shortly.

Although not completely documented, the URL should contain the user and password fields delimited as shown. Here is a good example:

jdbc:informix-sqli://mysystem:1526/stores7:informixserver=informix7;user=myuser;password=myuser;

Workaround: Use ODBC driver or use the supported JDBC 1.4 driver.

Per Development:
Resizing a bitmat may alter the view of the bitmap, such as the disappearance of line segments. This change was cause by a deliberate behavioral change in PB 5.0.04 where the default StretchBit mode was changed from BLACKONWHITE to COLORONCOLOR. This introduced the problem with lines in the black and white BMP images.

PB Version/build Occurs in Development Occurs in EXE
--------------------------------------------------------------------------------------------------
PB 5.0.04 NO NO

PB 6.0 GA NO YES

PB 6.0/620 YES YES

PB 7.0/5031 NO NO

Work-Around :
Use a LONG RAW column when clobs or blobs can be ROLLBACKed in script.

Customer reported this when connected to Microsoft SQL Server but it also occurs with Adaptive Server Anywhere. Loses between 1000-1500K per 9900 records processed. Similar results when run with PB 7.0 build 5031.

Each run represents processing of 9901 records
Using NT 4.0 Task Manager to see Memory Usage

Results when run with PB 6.5 build 620 and EA Studio
----------------------------------------------------------------------------------
Memory Difference
Memory Usage at Start 52344K 0
Memory after 1st run 53452K 1108K
Memory after 2nd run 54436K 984K
Memory after 3rd run 55836K 1400K

Close out of app 55712K
Close out of PB 6.5 Memory returned

Results when run with PB 6.5 build 620 and MSS SQL Server
----------------------------------------------------------------------------------
Memory Difference
Memory Usage at Start 45664K 0
Memory after 1st run 46956K 1292K
Memory after 2nd run 48124K 1168K
Memory after 3rd run 49284K 1160K

Close app PB still running 49150K
Close out of PB 6.5 42224K

This is a dangerous bug since it affects data entry, validation (and validation rules) and datawindow expressions using this date column.

Closely related to 197886 and 193284.

Example: enter 1999/03/05 in a retrieval argument dialog for a date column (May 3, 1999). The pbtrace.log shows:
1999-03-05 which is really March 5th, 1999.

IE. For SQL Anywhere, the PBDateFmt default in the PBodb<60,70>.ini is 'yyyy-mm-dd'.

Closely related to CR197884 and CR193284.

Development: We ask Windows what the date sequence is ( 0=m/d/y, 1=d/m/y, 2=y/m/d, note there isn't one for y/d/m). Windows says the sequence is "2" which is what we use.

Expanded note in User's Guide on date columns and regional settings. See pbman.chm dated 12/11/00 or later.

This requires the use of an edit mask. Sorry, not a bug and here's why; when we read a date column with no editmask, we ask windows what the date sequence is ( 0=m/d/y, 1=d/m/y, 2=y/m/d, note there isn't one for y/d/m). Windows says the sequence is "2" so we interpret that way. yyyy/dd/mm is kind of unusual as a date format and evidently isn't something Windows recognizes either. However, an edit mask ought to work fine for them.

As part of work on CR 193284 it has been determined that the support for yy/dd/mm will NOT be added to PowerBuilder in order to preserve the current applications that may be relying on the current behavior of switching to yy/mm/dd when yy/dd/mm is encountered. We believe that it is too high a risk to be changing at this stage and since this is a very unusual, an unsupported by WIN32 date format, we will not be supporting it.

It appears from the test case that uo_listener is the problem preventing
the rest of the uo's from showing in the list.

Workarounds: Export the uo_listener uo. Delete uo_listener. Import
the uo back into the pbl. Now when you go into the wizard all the uo's will
show up.

Another workaround is to modify the comments for uo_listener in the
library painter. When you go back into the wizard all the uo's will show up.

Exiting PB frees all the handles.

Other related handle leaks:
Saving an object leaks around 40 handles.
Going in and out of the library painter leaks 80 handles.

Several painters: Profile (350), DB (100), Function (100-110), Application, Project, Menu leak at least 50 handles opening them and 20-40 handles saving an object.

PowerDesigner generates such DataWindows in certain scenarios.

Development: This is actually a feature. In the case of objects with attribute moveable/resizable specified or when presentation style of grid, actions in preview will be reflected back to the design view. Forget, for a moment, the expression thing: with grid, resizing columns will immediately take effect in design. When expression has been set, we won't react immediately in design view BUT, as soon as you do another move of column in preview, we'll rebuild the whole dw in design based on how it currently looks in preview.
NOTE: You can also simulate this same behaviour using expression on an object that has moveable and/or resizable options set.

Additional regression in the Edit Tab of the Properties View in the DataWindow Painter is that in PB 6.5 if there is any change to any of the the properties the Style Name is removed but in 7.0 it allows you to make changes to the properties but the Style Name remains.

Additionally an enhancement to be able to remove the Style Name without the other properties changing would be helpful.

Note: Microseconds can be saved using the timestamp datatype.

PB procedure: The descendant object modified and it's parent need regeneration so that the parent is aware of
the descendant's changes - so regenerate object at current (level) and (level - 1).

In this scenario:
w_charity (Grandfather) has function wf_valid()
|
w_main (Father)
|
w_support (Child)

A cmdbtn on the ancestor window (w_charity) has this code:
boolean lb_test
lb_test = wf_valid() //call window function on ancestor

//////////////////////////////////
Window function: wf_valid() has the following code:
Long i, max_number_of_objects
boolean lb_success = TRUE , lb_newvalue = TRUE

string ls_str , ls_powerbuilder_object
ClassDefinition cl_def

max_number_of_objects = upperbound(Control[])

for i = 1 to max_number_of_objects
ls_str = this.control[i].classname()
ia_any = this.control[i].event dynamic ue_invest() //returns classdefinition instead of null value for ia_any if the family hierarchy has not be //regenerated after new control objects added to last descendant
//
IF IsNull(ia_any) THEN
messagebox('At grandparent Level 1:object ' + ls_str , 'NULL value returned from dynamic event call because this control does not have this User Event defined.')
ELSE
cl_def = ia_any
ls_powerbuilder_object = cl_def.classname()
if ls_powerbuilder_object = 'classdefinition' then messagebox('ia_any ', ls_powerbuilder_object )

lb_newvalue= ia_any //this line has problem with new control objects added to LAST/FINAL descendant only
//error msg- Cannot convert classdefinition to boolean from any value
// however if regenerate family hierarchy ,then works fine
if NOT lb_newvalue then lb_success = lb_newvalue //Change variable only if result is Boolean FALSE

END IF
next

return lb_success // return TRUE only if all control objects perused returned TRUE
///////////////////////////////

When controls are ADDED or DELETED on the last descendant window (w_support) the following error occurs:
PB Application Execution Error R0063:
Function/Event with no return value used in expression at line XX of wf_valid of object
w_charity.

The customer reported this problem when using User objects and user object functions.
I expanded my tests to use standard control like window objects with window functions.

PB6.5.444 and 70_5031 on Win98:
Type of object Type of function having dynamic call Result
Visual User object User object function in ancestor Broken
Window object Window object function in ancestor Broken

Testing log PB6.5.444 and 70_5031 on Win98:
1)
Add/Delete control on w_main, regenerate next descendant w_support.
Run app, call ancestor window function --> Result OK.

2)ACTION: Test dynamic event call in an ancestor window function:
Add new controls on last descendant w_support
Call ancestor window function --> gives error msg above.
Regenerate w_support, run app --> gives error msg above.
Regenerate w_main, run app --> gives error msg above.
Regenerate w_charity, run app --> Result OK.

3)ACTION: Test dynamic event call in a window function on last descendant:
a)
Cmdbtn on ancestor window has code:
boolean lb_test
lb_test = parent.function dynamic wf_pay()
b)
wf_pay() is a window function in the last descendant w_support which has the same code
as above for the wf_valid function.
c)
Add new controls on last descendant w_support
d)
Run app, call descendant window function --> Result OK.

causes a crash

workaround:
uo_1.of_additem(60, "Slisk")
uo_1.of_additem(70, "Hair")

Workaround:
use the trim() function with a return value.
Example:
string mystring
mystring = " hallo "
mystring = trim(mystring)

Workaround: Use Modify() to set the visible attribute of all objects you want to hide.

Work-around : add a proper changemenu call in the activate event of the sheets

Workaround: The setfullstate does not bubble up information into the "child" graph object but should. To get around this, you can do one of 2 things.

// force it to redraw by forcing the visible attribute to 1 (yes, it's already visible). Make sure you name the graph object "gr_1"
dw_1.getfullstate(blob_variable)
dw_2.setfullstate(blob_variable)
dw_2.object.gr_1.visible=1

// or
dw_1.getfullstate(blob_variable)
dw_2.setfullstate(blob_variable)
dw_1.filter() // This is a little more "destructive" - and might affect the data if you have a filter defined.

Works fine in 7.0.1 build 6012.

\powerbuilder 7 \code examples\HTMLdw in the Remote datawindow example pbl (PBDWRMT.pbl).

See TechDoc for PB 7.x & 8.x (#1013138)
Adding Customized Items to Wizard Generated To-Do Lists (PowerBuilder 7.x & 8.x)
http://my.sybase.com/detail?id=1013138

1. From a script painter - I have to open another script painter and select DECLARE (which is not intuitive), or use the popup menu and choose
GoTo | Instance Variables (which I can't do if I'm in the middle of a piece of script), or choose Edit... GoTo... Instance Variables from the menu.
Instance Variables whould be selectable from the View menu.

2. If I do NOT have a script painter open, I cannot get to instance variables at all. Why do I have to open a script painter to get to
instance variables? They belong to the object not the script.

3. If I do NOT have a script painter open, I can't get to Global Variables. I should have access to Global Variables from ANYWHERE. They're not tied to an object, but to an application.

When run on WIN 95 the resulting Excel report appears to actually be generated although when the number of rows selcted is greater than 2500 the error is still generated. When you exit PB and go into Excel the report appears to be complete. In NT 4.0 regardless of the number of rows the error is generated although again the actual report appears to be created properly.

When the macro is run directly through Excel or through OLE in VB 6.0 it runs without the problem.

Solution is to add the following line of code right before running the macro:

excelobj.SetAutomationTimeout( 900000 ) // 15 minute timeout

The documentation states that if you timeout you will receive a 1037 runtime error but in this case we received a R0035 instead.

Per Development:
No Bug -- DW design breaks the DW header/row size-restriction rules (it was only a fluke that it worked in 5.04 as this design is NOT supported). The user has the wrong DW design for the desired report. Instead of huge page headers and group headers, that break DW design rules, the data should be presented in a series of nested DWs. The nested DWs would ensure proper pagination.

Workaround: To recover object. Export the object in the Library Painter. Edit it to remove references to the instance variable and then reimport it back in.

Java package name is the name of the java "package" ( basically directory
off the Classpath ) that you will deploy generated stubs to. For example,
the way it is setup now, you will by default generate stubs to a directory
that is the same name as your Jaguar package. You can change this by
setting the "java package name" property in module properties in Jaguar
Manager. This is helpful when creating a commerical application as the
stubs should go in the "com" directory off the classpath. For us, the java
package names that we assign are something like com.dds.jaguarpackagename.
The problem that we are having is that we often have to deleted entire
modules and we lose these settings every time that we do. We have to go
into Jaguar Manager and set these properties for each module. It would be
nice if the PB deployment projects supported this property as well as the
other Jaguar properties that it does not.

In Jaguar there is pool timeout and transaction timeout.
In the PB project, only one is supported. If we change the other's value in
Jaguar Manager, it gets overwritten every time we redeploy.

Scroll functions tested:

ScrollToRow() // dw_test.scrolltorow(ll_nr)
ScrollPriorRow()
ScrollNextRow() // li_ret = dw_test.scrollnextrow()
ScrollPriorPage()
ScrollNextPage() // li_ret = dw_test.scrollnextpage()

Action:PB6.5.1 on NT4.0(Build 1381 SP3) in development environment.
Iteration RESULT
il_max=1000 | 2000 | 6000
No Scroll function in DO LOOP :
Before run app 60348K | 60944 | 60916
Exit App 60240 | 60948 | 60924 OK

With ScrollToRow function statement:
Before run app 61388K | 60864 | 60916
Exit App 62092 | 62000 | 63644 Leak

With ScrollPriorRow function statement:
Before run app 62212K | 60936 | 60924
Exit App 62148 | 60944 | 60916 OK

With ScrollNextRow function statement:
Before run app 62148K | 61996 | 60472
Exit App 62896 | 63532 | 63276 Leak

With ScrollPriorPage function statement: il_max = 10,000
Before run app 60516K | 60740 | 60568 | 60868
Exit App 60524 | 60840 | 60552 | 60912 Leak

With ScrollNextPage function statement:
Before run app 60516K | 57612 | 54432
Exit App 60516 | 57608 | 57580 Leak

2)
Action:PB6.5 on NT4.0(Build 1381 SP3) in development environment.
Result: No memory leaks with any of the scroll functions.

Fixed in 6.5 1048, 7.0.2 build 8025

As far as an enhancement request, giving the Footer band an option to only print
on the last page would do the job.

I would also request something a little more generic. I would propose what
I would call a "Positioning" band that the user could chose to put anywhere
(within any band) within a datawindow (maybe even limited to a report type
datawindow - one that does not allow updates). This "Positioning" band
would have characteristics as follows:

Have it start immediately following a previous item (autosize height) or
give it space increment (inches or powerbuilder units). The previous item
could be a previous band (top of the band or bottom of a band), or could be
the top or bottom margin of the datawindow (report).

It would be nice if it would allow you to specify that this "Positioning"
band would have some "Page" mode options such as 1) no page break, 2) always
start a new page or 3) start a new page if less than xxx inches/pb units
available on bottom of page."

====
Resolution:

There was a fix in pb6.5 for issue # CR 183803 that was made specifically to change the behavior of ListView Right Mouse processing. With this fix, the behavior should match what is expected and that is in fact why the behavior changed between builds mentioned in the description.

In PB7, we are using Microsoft's ListView and TreeView controls and the behavior we are seeing is the way it is intended to work per Microsoft and we cannot change that behavior without doing something very ugly in PB which we want to avoid doing. In PB7 the rbuttonup is never received by the application, however, this is the way Microsoft has coded it.

dw_1.retrieve(24,24) will send to the server as 24,00

If you specifiy the retrieve like

dw_1.retrieve(24.24) will send to the server as 24,23

Using Open Client 11.1, ASE 11.5, pb 6.5 with windu 4.2, netscape 3.61 web server.

NOTE: Using lv_1.setredraw(true) will display the items when you scroll them back on the screen. Unfortunately, there is no event that captures this easily (no pbm_mousewheel) to script a setredraw(). An enhancement has been entered for this support.

The error you get from the driver is:
SQLSTATE = 37000 [Microsoft][ODBC Microsoft Access Driver] Reserved error (|); there is no message for this error.

The fixes are in the PBODB70.ini from 7.0.2 and above.

OLD PBODB70.ini
============
[Access]
PBDateTime='DEFAULT_DATETIME'

[DEFAULT_DATETIME]
PBDateFmt=''{d '\'yyyy-mm-dd\'' }''
PBTimeFmt=''{t '\'hh:mm:ss\''}''
PBDateTimeFmt=''{ts '\'yyyy-mm-dd hh:mm:ss.ffffff\''}''

NEW PBODB70.ini (7.0.2 and up)
=============
[Access]
PBDateTime='NO_MSECS_DATETIME'

[NO_MSECS_DATETIME]
PBDateFmt=''{d '\'yyyy-mm-dd\'' }''
PBTimeFmt=''{t '\'hh:mm:ss\''}''
PBDateTimeFmt=''{ts '\'yyyy-mm-dd hh:mm:ss\''}''

The newer driver you're using requires this format.

You can prove this is the cause issuing the following SQL:
Select {ts '2000-05-24 14:48:19.580000'}
vs a
Select {ts '2000-05-24 14:48:19'}

The first (using the old PBODB70.ini formatting) gives the 37000 error, the new
formatting doesn't.

This is easy to work around by just opening the script and deleting the code, but it should not happen.

Following calls always return -1 :

lv_1.FindItem(0, DirectionDown!, True, False, False, False)

lv_1.FindItem(0, DirectionDown!, False, True, False, False)

Workaround :

Replace DirectionDown! by DirectionAll!

For example, open window painter (any object painter would do) and paste the following into the declare instance var pane...

string is_1[2000]
string is_2[2000]
string is_3[2000]
string is_4[2000]
string is_5[2000]
string is_6[2000]
string is_7[2000]
string is_8[2000]
string is_9[2000]
string is_10[2000]
string is_11[2000]
string is_12[2000]
string is_13[2000]
string is_14[2000]
string is_15[2000]

Takes around 15 seconds to save this window. Change this to shared, global or local and it takes a fraction of a second

This is the script tested in my pbl:
//Test memory leak when multiple function calls made
int li_count
string ls_app_name
FOR li_count =1 TO 20000
ls_app_name = Left(Lower(GetApplication().AppName),
NEXT
Messagebox ('Iteration','Done 20,000 times ')

a)
Tested ls_app_name = Left(Lower(GetApplication().AppName),
NT4, PB 6.5.444 10,000 | 20,000 | 30,000
Before start app 59560 | 59536 | 59560
Exit application 59556 | 59552 | 59556 Sometimes Leak

b)
Tested ls_app_name = Left(Lower(GetApplication().AppName),
NT4, PB 6.5.1 10,000 | 20,000 | 30,000
Before start app 59748 | 59748 | 59768
Exit application 59748 | 59764 | 59768 Sometimes Leak

Example:
a.pbl with an ancastor object ---- w_ancastor
b.pbl with an descendant object ---- w_descendant

If you scripted the systemerror event and you use the FindClassDefinition() function in the following way, then the systemerror is not fired.

ClassDefinition myDefinition
String ls_class[]
ls_class[1] = "c:\b.pbl"
myDefinition = FindClassDefinition("w_descendant", ls_class)

then a systemerror occurs because the classdefinition can't be resolved by BowerBuilder, becuase the a.pbl is not specified in the ls_class string array. This systemerror does not fire the systemerrror event in the applicationobject.

However if anything but the whole selection of the column item is made, PB triggers
the EditChanged and ItemChanged Events correctly :
e.g. If the item is 123.4 then highlight 4 and press BACKSPACE or DELete and PB will
trigger the EditChanged and ItemChanged Events.

This problem is not specific to any country regional setting therefore decimal separator
of '.' or ',' is irrelevant to the issue.

Select/ Highlight whole column item, the EditChanged and ItemChanged Events are not
triggered by default in PB. This is broken for all versions below:
PB 6.0.251
PB 6.5.444
PB 6.5.1
PB 7.0.5031
Pb 7.0.1.6005

If the column has an editmask with NO decimal positions defined e.g. ### with datatype dec(2), the events are triggered correctly.

myfunc is a function that returns a structure. The structure contains two string fields, and the values are initialized properly.

Using 5.0, the following code worked. Migrated to 6.5, and tested using 7.0, the code returns garbage in foo.

string foo

foo = myfunc().field1

Per PB Engineering:

The reason this worked in 5.0 was because we were not deleting the temporary struct returned from the function call in the expression myfunc().fieldname. This resulted in a memory leak which has since been fixed.

As part of fixing this memory leak, the field elements were also free'd after the expression evaluation. Because the field here is a string, the string value therefore is free'd resulting in the garbage that you see when you run this test case.

It is expected that this syntax will work for simple data types at this time, but not for strings, or arrays.

Please issue a separate change request for a compiler warning against this, to eventually be a compiler error in the next major release of PB. Due to this, I would strongly recommend to customers that they change all occurrances of this syntax to use a local struct variable, and return the function result into that. This ensures that the data will be correct and avoid any crashes until we fix the compiler to warn against this.

(CR 203969 was added to request the compiler warning.)

Fixed in 7.0.1 and beyond..

<INPUT value=<!--EVALUEATE EXPR="addQuotes(mydate)" --> >

When a change is made in page view then the following gets changed to

<INPUT value="<!--EVALUEATE EXPR="addQuotes(mydate)"> >

Case originated from issue 41042980

Another example is

<input value=<% =Session("somevalue") %> >

which is changed to <INPUT value=<%" Session> >
when a change is made using Page view.

While I was at it, I searched to see what exactly RawData=1 does. It is no longer used by the WinSock Driver, and therefore does not have any effect on a DPB application.

This information is true for PB65 and up. I don't know exactly when it was removed, but I know it is not there in PB65 winsock driver.

Workaround: Use SDK.

Function boolean SetWindowPos(Long hWnd, Long hWndInsertAfter, integer X, integer Y,integer cx, integer cy, UINT uFlags) library "user32.dll"

Code to set window to Top:
// get pixels for API calls

long lx,ly,lwidth,lheight
lx=UnitsToPixels ( x, XUnitsToPixels!)
ly=UnitsToPixels ( y, yUnitsToPixels!)
lwidth=UnitsToPixels ( width, XUnitsToPixels!)
lheight=UnitsToPixels ( height, yUnitsToPixels!)

boolean rc
rc=SetwindowPos(hwnd, -1,lx,ly,lwidth,lheight,64)
if not rc then
messagebox("Problem", "Problem with setwindowpos, "+string(rc))
end if

=======

To return to normal
SetwindowPos(hwnd, 1,lx,ly,lwidth,lheight,64)

NOTE: The x,y,width and height in the UnitsToPixels code assume this code is in an event of the window itself (not under a command button where this will cause problems)

Additionally the terminology should be consistent as the RMB options refer to parameters while the painter uses arguments.

Instance variables defined in an ancestor window display in a descendent window

If you create a window by inheriting it from an existing window that has public or protected
instance variables with simple data types, the instance variables display and can be modified in
the descendent window's Properties view. You'll see them at the bottom of the General tab
page.

ENHANCEMENT REQUEST: Allow Drag and Drop of these ancestor Instance variables that are on the property sheet.

Workaround :
1) set oracle NLS_NUMERIC_CHARACTERS parameter to '.,' and set decimalSeparator dbparm to '.'
OR
2) set decimalSeparator dbparm to '.' and just after your connect statement in scripts add the following statement : execute immediate "alter session set NLS_NUMERIC_CHARACTERS='.,'";

SQLCA.DBMS = "ODBC"
SQLCA.AutoCommit = False
SQLCA.DBParm = "Connectstring='DSN=PowerBuilder Demo DB V6.0;UID=DBA;PWD=SQL'"
connect using sqlca;
ids_data = create n_ds
ids_data.dataobject = "d_multi"
ids_data.SetTransObject(sqlca)
// 1. retrieve
li_rc = ids_data.Retrieve(1)
li_rc = ids_data.GetFullState(lblb_daten)
li_rc = dw_1.SetFullState(lblb_Daten)
// 1. change
dw_1.object.text[1] = "change"
li_rc = dw_1.GetChanges(lblb_daten)
li_rc = ids_data.SetChanges(lblb_daten)
li_rc = ids_data.Update()
li_rc = ids_data.GetChanges(lblb_daten)
li_rc = dw_1.SetChanges(lblb_daten)
// 2. changes
dw_1.object.text2[1] = "change"
li_rc = dw_1.GetChanges(lblb_daten)
li_rc = ids_data.SetChanges(lblb_daten)
li_rc = ids_data.Update()
li_rc = ids_data.GetChanges(lblb_daten)
li_rc = dw_1.SetChanges(lblb_daten)
// 2. retrieve
li_rc = ids_data.Retrieve(2)
li_rc = ids_data.GetFullState(lblb_daten)
li_rc = dw_1.SetFullState(lblb_Daten)
// 1. Change
dw_1.object.text[1] = "change"
li_rc = dw_1.GetChanges(lblb_daten)
// SetChanges returns -2 !!!!!!!!!!!!!!!
li_rc = ids_data.SetChanges(lblb_daten)

Workaround :
// insert following lines just before the 2. retrieve
ids_data.dataobject = "d_multi"
ids_data.SetTransObject(sqlca)

NOTE: This works fine if the data is RETRIEVED from a database.

Characters such as @#%^&*()&^! <>?": don't show up. Works ok with the windu
4.0 version.

PB 7.0 added the optional dialog to overwrite when a name conflict was found during the copy.

The enhancement would be to have a dialog that had {YES to ALL} {YES{ {NO| {CANCEL{ as many "install" programs have.

"Print Error" (Print Failed. Report Terminated).

')' expected after function name. This does not happen with 2 arguments or at all in 6.5

Per Development, this is not a bug:
This issue does not describe a bug, but a misuse of DPB. To avoid the threads from remaining, you must use the timeout feature available in DPB as follows:

There is a feature on the Transport Object where you can set the Timeout Property and it will tell the DPB Server to disconnect the client after some amount of time of inactivity. The value that you set this property to is documented to be in seconds, however, I have found that it is actually in milliseconds, therefore 1000 would tell it to wait only 1 second.

Inactivity could mean either of the following:

- The client is sitting idle and not making requests to the server for the timeout interval
- The client has been shut down abnormally due to power outage or network cable being disconnected.

For this reason, you must be careful when setting this value to an unreasonably low value, such as 1 second.

The intended use for this feature was to have the customer code in the client application, a polling mechanism that would continually issue some function call or remote object property get/set repeatedly while the client is running so that when the client is abnormally shut down, the server would detect this and do the necessary cleanup. This polling would only take place during what otherwise would be idle time for the client application.

When this timeout property on the transport option is NOT set, there is NO timeout and the server will never detect a client has been disconnected abnormally. In the case of a normal shutdown where the client actually issues a disconnect from the server, the server does handle the necessary cleanup.

2 workarounds:
1) Install latest NTWDBLIB.DLL (a version from 1998). 1995-1997 versions causes the problem. This requires that the customer contact Microsoft and upgrade their Client Software for MS SQL Server 7.0. This seems to get rid of the problem.
2) To keep existing software, add benign dbparm to apps and DB profiles. Ex: sqlca.DBParm="appname='mssapp' ". Adding anything to the DBPARM gets rid of the huge memory usage. Setting the "Application Name" on the "Network" tab of the database profile painter is benign and the best solution. This puts "appname=myapp" in the DBPARM.

The problem is the PBSYC2.SQL script SP_pb60table, SP_pb70table procedures that are used in several places to bring back the table list. This script doesn't have the necessary SQL in the stored procedure to pull the tables accessable through roles to the Powerbuilder 'Select Tables' dialogs. (This script is supposed to support only bringing back tables the user has access to)

You can use the PBSYC.SQL version of sp_pb60table, sp_pb70table (which brings back ALL tables whether you have permission or not) as a workaround.)

NOTE: If you get the following error: Select error: "select permission denied on object XXXXX(table name)", database (database name), owner (dbo). Do you want to correct errors?

after adding the roles, you might have forgotten to ACTIVATE the role by doing the following in ISQL:
sp_modifylogin User1, "add default role", Role1
go

(the example assumes a user of 'User1' and a role of 'Role1'

No workaround available

I have discovered that if there are sub-menu items on the second level in a certain scenario the clicked event of a particular menu items do not get fired.

When using PB 6.X and connected to Microsoft SQL Server through the ODBC driver downloaded from the Microsoft Web Site you will receivean error similar to

pb60.exe Aplication Error

The instruction at '0x10bff94c' referenced memory at '0x033c00a'. the memory could not be read.

This applicaiton is using shared objects.

This does not happen on the first Selectblob but on the second or a subsequent one.

This is not a problem when connected to MSS thorugh or native driver and it was not a problem when connected to ASA through our ODBC Driver.

FAILS Tabular style PB6.5.444 on Win98, NT4:
In the PrintPage event of the datawindow control for Tabular style dw:
// PageNumber is an argument in the PrintPage event:
if pagenumber > 1 then
li_ret = integer(dw_1.Modify("Datawindow.Header.Height=0")) //Make the header band of the dw equal to zero height
else
// on page 1
end if

Result Tabular/ Freeform style PB6.5.444 on Win98, NT4:
Page 1 : Header and column data displayed correctly
After Page 1:
Header is not displayed after page 1 (correct result)
Duplicate data of page 1 is repeated on next pages.
Page() function evaluates to page 1 on all pages instead of counting as second page, third page etc.
The number of pages output on printer is correct however data of page 1 is displayed on all pages.
Printing to PSR format produces the same result.

Using a composite presentation style.
On this composite(d_composite) there are 2 datawindows d_titles and d_emp:

In dw d_titles, the label names of the columns are text objects and placed in the Detail
band with Autosize height set to yes/ true.
D_composite:
a)In the header band of d_composite, place a report object dw (d_titles) which contains the
header information for the final report e.g. Cust ID Cust Name
b)In the detail band of d_composite, place a report object dw (d_emp) which contains the
detail information e.g. Cust ID column object Cust Name column object
In the Detail Band object, select Autosize height to yes/ true.

WORKS Composite style PB6.5.444 on Win98, NT4:
In the PrintPage event of the datawindow control for Composite style dw:
// PageNumber is an argument in the PrintPage event:
IF PageNumber > 1 then
This.Modify("DataWindow.Header.Height='0' ") //Do not display header info after page 1.
//or This.Object.DataWindow.Header.Height='0'
END IF

NOTE: Duplicate of CR197962

To workaround, modify the script to write out the entire tag, instead of a portion of it.
For example, instead of using script like this:
<INPUT value="
<!--SCRIPT
document.writeln(Math.random());
-->
" id=INPUT2 name=input2>

Use script instead that generates the entire tag:
<!--SCRIPT
document.writeln("<INPUT id=INPUT2 name=input2 value="+Math.random()+">");
-->

Problem happens for getfullstate/setfullstate and when the original buffer
is changed.

Error is : unhandled exception in pb70.exe (pbdwe70.dll) 0xC00000005:
Access Violation

Development: This is intended behaviour! as soon as you click on a view other than design view, we force the taborder processing to be
turned off. Consider it a bonus that you can do some extra processing via the toolbar when tab order is on!

This works OK sending to postscript printers.

HP Information and drivers
http:/www.hp.com/euro

Microsoft Information
http://www.microsoft.com/windows/euro.asp
(for example to get NT4_euro.exe from the Microsoft site)

The important thing is to see the Euro, you have to have an Editmask on the column of [currency(7)] or [currency(n)] and on the Regional Settings, Currency Tab, you must select the Euro as your currency symbol.

Workaround:
Turn on 'Print Text as graphics' in the printer driver print setup (HPIV printers). There is still a problem with the HP PCL driver.

For HP IV drivers
Document Options
Print Text as Graphics=ON

Other drivers might be affected. The datawindow engine PBDWE60.DLL after build 570 is causing the problem.

Per Development:
No fix is possible for this one. In this condition, Windows is sending the Editmask code an unexpected BS causing us here to lose track of characters and where they belong. Under many similar conditions this caused a loop until an eventual GPF. In 7.5 this is fixed by reworking how the Editmask code writes data to the control. This particular fix would be much too destabilizing for 6.5, 7.0. Editmask controls should be sized large enough to contain all of the data.

Workaround: other column styles are working correctly. Use a different style, such as Radio Button or ListBox.

HTMLDW, HTML DW

GDI is lost manipulating text objects (changing fonts) but you can see the leak going into and out of the painter.

Eventually invalid page fault (GPF) in KERNEL32.DLL 0167:bff9db61

This worked in 6.5.1, 7.0 GA.

Must return to SQL, change something in the SQL (add/remove a column from SQL), now the computed column is visible

Happens with even the newest ODBC Driver 3.70.0623 SQLSRV32.DLL. Note that retrieval arguments work fine when they are not embedded in the sub-select.

Workaround: Use disablebind=1 in the DBPARM or check disablebind in the profile in development.

When a drop down DataWindow contains a retieval argument it can not be used in a Web DW as their is no way of programmatically specifing the value of the retieval argument.

Also if you resize the dw on the window the rectangle comes into foreground and
hides some of the fields even though its suppose to remain in the background. (Rectangle object
is behind the text objects (Sent to back))

Workaround:
The header band of the dw has a rectangle object and column text objects on it.
If you take away the rectangle object than problem goes away.

Starting in build 520 the menu is not redrawn when visibility is changed so the new menu item is not visible. As setredraw() does not apply to menus it is not possible to force the menu to redraw after the dynamic changes have been made.

Per Development, This is Not a Bug.
By product of new way menus handle visibility changes.
This is probably a change in behavior rather than a bug. The change in behavior is probably a result of the several bug fixes dealing with changing the way menu visibility is handled internally. Refer to the resolution for CR 184160 for more explanation.

Most often reported as "RED" text doesn't print using NT 4.0 and HP printers on the final printout.

Workaround: Go into the datawindow painter and RE-SAVE each column where you have text with non-black color. You will see the background.color of the text change from ' 536870912' to '553648127'. When the background.color is 553648127, the (for example) RED text will show up on printed output. You can also change the background to WHITE for all the columns with RED/text with color but this only works on white background datawindows.

Also: Notice to ADD another computed column, you hit the TAB key (not intuitive) as the ENTER key does nothing. BOTH keys should add rows as it did in 6.5 and in 7.0 in the database painter "add column" mode. The tab key should add a row when at the last field of a row and the ENTER key should add a row no matter where you are.

This seems to work fine in 7.0.1 (7.0 build 6012)

They show up as edit style instead of as DDDW's.

To reproduce:

Create a freeform style datawindow on employee.

Create a tabular style datawindow based on dept_id and department_name from department

Edit the dept_id column on the employee datawindow so it is of type dddw and uses the datawindow based on department.

Convert both datawindows to syntax in the Design menu of the painter where you can choose tables and columns.

Use the DW DTC to create a page based on the datawindow. Deploy the page. Notice that the drop down does not appear.

As the purpose of unchecking the "Allow Dashes In Identifier" checkbox specifically allows you to do this, a-b when this is unchecked should be interpretted as subtraction.

Workaround: As in CR154227, while Windows95 refuses to write any date with MMM clause to the WIN.INI file, you can manually set it.

NT 4.0 has a different behavior. The best way to insure consistency in Win95/98 platforms is to check the Registry "sShortDate" setting and compare it with the win.ini. If they are different, the developer has 2 choices.
1. Notify the user to change the win.ini to match the Registry and shut down the application.
2. Modify the win.ini based on the registry settings for sShortDate in code and notify (or not notify) the user.

// win.ini section that has sShortDate setting
[intl]
sShortDate=mm/dd/yy

// code to check 32 bit WINTEL platforms
environment env
integer rtn
string ls_shortdate, ls_shortdateini
int rc

// Check Win95/98 or NT environment
rtn = GetEnvironment(env)
IF rtn <> 1 THEN RETURN
CHOOSE CASE env.OSType

CASE Windows!

RegistryGet("HKEY_CURRENT_USER\Control Panel\International", "sShortDate", ls_shortdate)
ls_shortdateini=ProfileString("win.ini", "Intl", "sShortDate", "None")
if lower(ls_shortdate) <> lower(ls_shortdateini) then
messagebox("Date Error", "Registry setting does not match win.ini")
return
end if

CASE WindowsNT!
// calls get redirected to the registry. The sShortDate does not have to be in the win.ini.

CASE ELSE
RETURN

END CHOOSE

Use a tabular datawindow which accesses the Employee table of the EA Studio 3.0 Demo DB. It has a Next and a Previous button on it. We tested the first row, firstname column. In our database, the initial value retrieved from the database for that row/column is "Fran".

Using Internet Explorer 4.0 and 5.0:
1. Bring up the datawindow (html file) in the browser. Initial Data value = "Fran"
2. Change Fran to Fran1.
3. Click Next
4. Click the Browser's BACK button. The data value displayed reverts to "Fran"
5. Change Fran to Fran2.
6. Click the Next button.
7. Click the Previous button. We expected to see "Fran2", which was the last thing we entered, but the
data value at this point is now "Fran1", which was not expected.

Using Netscape Nav 4.04, Communicator 4.04 and 4.51:
1. Bring up the datawindow (html file) in the browser. Initial Data value = "Fran"
2. Change Fran to Fran1.
3. Click Next
4. Click the Browser's BACK button. The data value displayed is "Fran1" but when you click on the column, it reverts to "Fran"
5. Change Fran to Fran2.
6. Click the Next button.
7. Click the Previous button. You see "Fran2", which is what was expected.

Something like:
string ls_state = "NY"
long ll_index
For..
dw_1.Object.state.filter[ll_index] = ls_state
Next

Workaround: Since dot notation in the Primary buffer works, invert the filter so the rows to be modified are in the primary buffer (Not {filter expression{) then apply the filter when done modifying (via dot notation) against the primary buffer.

Ex: If the filter is "state='MN'", make it NOT(state='MN') and change the dot notation filter to:

dw_1.Object.state.primary[ll_index] = ls_state

then apply the real filter "state='MN'"

Add a button to a page containing a Web DataWindow

<INPUT TYPE=BUTTON VALUE=SetRow onclick="alert(dwMine.SetRow(3))">

Deploy page and click the button before clicking on the DataWindow

Add a button to a page containing a Web DataWindow

<INPUT TYPE=BUTTON VALUE=GetClickedRow onclick="alert(dwMine.GetClickedRow())">

Deploy page and click the button before clicking on the DataWindow

WORKAROUND: Get the current row before calling DeleteRow, and pass the correct row number instead of using 0.

DW ItemError Event incorrectly identifies NULL Values as dates with a column that has the required option set and also has a Date EditMask.
- NULL in an EditMask of MM/DD/YY will incorrectly identify the value as 2000-01-01.
- NULL in an EditMask of MM/DD/YYYY will incorrectly identify the value as 1900-01-01.

Note: The dates listed are the internal PB format which is returned by the ItemErrorEvent regardless of what the EditMask is set to.

On Solaris 2.5.1 with PowerBuilder 5.0.04, when the client application connects to the server application, memory is allocated each time. But when the client application disconnects from the server application the memory is NOT de-allocated. I have also tried the same application on WIN NT 4 SP 3 the memory is allocated and de-allocated accordingly for each client connect/disconnect.

NOTE: The problem also exists with PowerBuilder 6.5 on Solaris.

Workaround: User must use Control-Enter.

This works correctly in 7.0 build 6012.

\\network\this_is_my_very_long_printer_name_longer_than_32_characters

The 'name' is the part after the '\\network'.

struct mystruct
long field1
string field2

mystruct myfunc ()
:
return mystruct

///////////event or function script:
string lstr
lstr = myfunc().field2

See Jaguar CR 202352 for status.

Development: A new dbparm 'StripParmNames' has been added to remove parameter names around 7.0.1 build 7020. If this dbparm is set to 'Yes', all parameter names will be removed from generated call escape syntax. Note that this means that values passed will be inserted in the order passed regardless of the associated parameter name.

However, if you call Update (even though NAN displayed, the data is updated ok and the display is fixed properly.

Per Development:
If no columns have tab order, and the datawindow is not updateable, a button which is associated with the Update action will not be rendered in the browser.

VM=7.0 6012, DWE=7.0 6012, Database=MSS, 7.0 6012.

This is similar to what we do for stamping exes..

This also shows up with similar datawindows when migrated from previous version of PB.

// str_test contains only one string var
str_test lstr_Tests[]
any la_Param[]
la_Param[1] = lstr_Tests
Classname(la_Param[1]) // gets a gpf

1. Enter pb70 at the command-line prompt.
or
Click an icon linked to Powerbuilder (if you added it to the desktop).

This last sentence should be expanded to direct customers to their
System Administrator or System documentation.

Workaround: Even older versions of the datawindow engine would work with dropdowndatawindows (generate a TABINDEX correctly) if the "always show arrow" was off.

When trying to update the datwindow the following error is received. The value appears to always be the timestamp of the first row in the table.

"The error is: "The timestamp (changed to 0x00010000013da7f5) shows that the row has been updated by another user.

No changes made to the database."

Fixed in all builds after 7015.

This problem has been fixed in both pbdwe70.dll and pbsyc70.dll.

To correct this problem an enhancement to the stored procedure update method that includes a TIMESTAMP column was added to these dlls.
To support this new feature, one needs to use the correct technique for coding the update method. An example follows:

create procedure shk_timestamp_upd (@int_col_new integer, @int_col_orig integer,
@string_col varchar(25), @timestamp timestamp output )
as
update shk_timestamp set int_col = @int_col_new, string_col = @string_col
where int_col = @int_col_orig and timestamp = @timestamp
if @@rowcount > 0 and @@error = 0
begin
select @timestamp = timestamp from shk_timestamp where int_col = @int_col_new
end
else begin
raiserror 20001 "Update Procedure Failed."
end;

Several things are significant:
1) You need input arguments for both the original key field value (@int_col_orig) and the new key field value (@int_col_new) since we must include @int_col_orig in the where clause.
2) Declare the @timestamp argument to be of datatype timestamp. Make it an input/output parameter in order for datawindows to automatically refresh itself with the new value.
3) Don't use "where tsequal(timestamp, @timestamp)" in the where clause. Specify "timestamp = @timestamp"
4) Immediately after the update, check @@rowcount. If @@rowcount = 0, you did not update the row even if there were no errors reported.
5) If @@rowcount > 0 and @@error = 0 then it is the responsibility of the stored procedure update method to refresh the @timestamp output parameter with the new timestamp value from the table. This technique should work correctly even if there are update triggers associated with the table!

At this point, stored procedure updates of Timestamp columns will only work with PBSYC70and PBMSS70 They will most likely fail when connected to PBODB, PBOLE, and PBJDS.

If you try to run an Update() on the destination datawindow of the Setfullstate(), you will get:

"-3", "Row changed between retrieve and update"

This is fixed after 7.0.1 builds around 7010 (July 8th, 1999 or newer). This enhancement now copies the blob totally including the original buffers and should clear up a lot of problems with sql generation using SetFullState().

In the library painter, if you choose the directory level in the treeview, the available PBL's are displayed in the List View. If you then RMB on a PBL, choose properties and enter a commen,the comment is not displayed until you refresh the view. Customer feels this should automatically refresh when a property is changed.

The Serial column displays numbers like: 12344, 12600, 12856, 13112.

If you do a retrieve on this same table using the native driver the serial column displays: 80, 81, 82, 83, as it should.

WORKAROUND: In the PBODBxx.INI file go to section:

[INFORMIX_SPECIALDATATYPES]

SpecialDataTypes='MONEY=DBI_TYPEMONEY=100,SERIAL=DBI_ULONG=101'

change SERIAL=DBI_ULONG=101 to SERIAL=DBI_LONG=101

*** THIS BEHAVIOR DOES NOT HAPPEN WITH THE NATIVE DRIVE (IN7) ***

The codeexample is: dw_1.object.dept_id.EditMask.ReadOnly="No"

Workaround:
Set the spin property to no after setting the readonly property to no,
like: dw_1.object.dept_id.EditMask.Spin="No"
This will prevent the spincontrols from showing up in the datawindow.

Workaround:
use dw_1.post retriev() instead of dw_1.retrieve()

Related to length of printer driver name and mapping name.

The actual problem can be reproduced with any printer driver. It has to have the characteristics of it's "name", "port", "driver name" and "mapped name" to exactly equal 64 bytes. (we build a structure of these elements internally that causes this behavior - the user would never know this).

Also, the OBJECT BROWSER right-mouse support using "Document.." causes a window with a rich text edit control to appear and data to be written in the development environment. This also GPFs in PBRTC70.DLL.

NOTE: This doesn't seem to happen on ALL Win98 or Win95 machines.

Workaround: Point to a different mapped printer or create a new printer and use a shorter name.

The fix requires only PBRTC70.DLL in builds > 7.0.2 8027.

(WebDW, HTMLDW)

PER DEVELOPMENT:
When the update fails (for ANY reason), the Generate() method is getting back null and having an exception thrown.
This is fixed by setting a property on the DataWindow/HTMLGenerator component:
com.sybase.jaguar.component.tx_outcome=failed
This should be done manually using Jaguar Manageger in 3.0.x (and will default correctly in 4.0):
Open the DataWindow/HTMLGenerator component properties in Jaguar Manager.
Go the all properties tab
Set
com.sybase.jaguar.component.tx_outcome=failed

In order for a button that updates or inserts into a web datawindow to appear in the generated HTML, the datawindow must be updateable and have at least 1 column with a tab order. The problem with this is that there is no indication to the developer, who will waste hours of time trying to figure out why it does not appear. It would be better if it would generate the button disabled or something similiar as an indication rather than asking the developer to figure out why it never appears.

Some of these error messages are:
Wind/U Error (234): Function SetScrollRange, must only be called from the primary thread.
Wind/U Error(237):Function CreateSolidBrush, GDI API's must only be called from the primary thread
Wind/U Error(234):Function GetFocus, must only be called from the primary thread
Wind/U Error(234):Function GetClassName must only be called from the primary thread
Wind/U Error(234):Function RedrawWindow must only be called from the primary thread
Wind/U Error(234):Function InvalidateRect, must only be called from the primary thread
Wind/U Error(234):Function UpdateWindow must only be called from the primary thread
Wind/U Error (234):Function GetDC must only be called from the primary thread
Wind/U Error (234):Function ReleaseDC must only be called from the primary thread
Wind/U Error(234):Function RegisterClipboardFormat must only be called from the primary thread
Wind/U Error(234):Function SetCursor must only be called fromt he primary thread
Wind/U Error(234):Function ShowCursor must only be called from the primary thread

Workaround: Full Rebuild.

Workaround :
Connect with a system user ( = sysadmin server role checked for this user in MS SQL SERVER 7 for example )

Workaround:
Set height and width column/computed field properties to 0

Per Development, this is not a bug:
The Column Specification view has become the replacement for modifying external/stored procedure datasource information ... if you open this Column Spec view and rightmouse, you'll see an item "Stored Procedure..." that allows you to modify whatever.

The sample NVO has 50 object functions. One of the object functions has 110 arguments.

1. Absolute paths in the painter when translated to HTML show ' e:\program files\common files\holes.gif ' which in a browser will never translate to a picture when you click on Design/HTML Preview. This is just a simple rendering for the datawindow painter.

It's part of a more generalized problem in that the HTML generated (dw or ds.HTMLGen) should (suggestion) always be missing the full directory path or the code on the server should substitute into the datawindow where this is being generated (via dot notation) the actual Web Server Virtual directory path to the images stored on the web server - ie something like /images/holes.gif instead of e:\pb7\images\holes.gif)

2. The HTML DW source (dwtemp.html) is copied to the \windows\temp directory but the .gif files are not. The browser doesn't search the path for the .gif file. Since this html file is not returned by a server (with the .gif too), unless we physically check the dw for picture objects and copy the files to \windows\temp, they won't display in the painter.

A workaround could be to copy the .gif files manually to \windows\temp, change the location of the .gif from FULL path (e:\pb7\images...) to simple filename "holes.gif" and try Design/HTML Preview again. (if the browser cache doesn't find the new page, you may have to click on the refresh or reload button or Control-Reload to get the new page.

Workaround: The user has the ability to use a workaround of using .bmp files on the hard drive for the datawindow button pictures.

The object will also import correctly from the library painter.

The second client application might fail with a R0002 Null Object Reference. The server log shows:

SMI02 Connection <X> ERROR OCCURRED: The request caused an abnormal termination. The connection has been closed 80042008.It's

Another possible message: You might get a createinstance error return value of 55, which is defined as request terminated abnormally. If you run just one client createinstance will succeed. If you create a pcode executable of the server app this will succeed.

Using a webserver and pbcgi60.exe, the error is:
The instruction at 0x100034d5 referenced memory at 0x00000000. The
memory could not be read.

When you click ok, the following error message appears in the browser:
CGI Error:
The specified cgi application misbehaved by not returning a complete
set of HTTP hearders. The headers it did return are:

Also ran a test with pbisa60.dll and same problem but the error message was
No document header

Fixed in 6.5 build 1108 and above and 7.0.1 build 7022 (after the MJD 7021 build - Modified Julian Date)

(b) The sub-bands should each have their own attributes such as auto-size, 'suppress if empty', and 'suppress if true' based on a formula.

A major use of this might be to have a variable heading. For example when printing an invoice you might want to show a lot of information such as the invoice number, customer's name and address, ship-to address, etc. on the first page but only show the customer name and invoice number on subsequent pages. In this case you could create a header-a and a header-b. Header-a would be printed for page 1 and header-b would be printed for all subsequent pages.

There should also be a 'snap-to-allignment-bar' option.

*I let cust know that while there are no allignment bars, there is a snap to grid option - and the granularity of the grid can be adjusted. You can also lasso or select several fields at once and move them as a group.

While it is possible to create a datawindow, I usually would use an n-up presentation style, and create a data table it is a lot of work and does not look as if it is really part of the graph. This is especially true when there are several series and it is necessary to have the series descriptions appear both as legends on the graph and as text on the data table.

This issue is the same as Change Request 188839. This issue found the problem to be a variable is set to "~142" could not be compiled. pfc_n_cstfilesrvunicode happens to be the first one the compiler hits - all of the pfc_n_cstfilesrv(hpux,win32,aix,sol2) have this coded somewhere.

workaround: use toolbar

In the database if the column is varchar, PB7 shows as a char.
In the database if the column is datetime, PB7 shows as smalldatetime.
In the database if the column is money, PB7 shows as smallmoney.
In the database if the column is numeric, PB7 shows as decimal.
In the database if the column is nvarchar, PB7 shows as nchar.
In the database if the column is varbinary, PB7 shows as binary.

The datawindows created from these are generally correct. Varchar and char become char in the datawindow and so on.
The worst one is the Money datatype since it becomes Decimal(0) in the datawindow instead of Decimal(4). Powerbuilder uses can export the syntax. Datawindow Builder users (PowerJ) and InfoMaker cannot fix this and the fractional part will be truncated to "0"

Also, if you have a datawindow containing an outer join in the where clause and you examine it using the OLEDB interface, you'll see it blows away the where clause to something like:

WHERE ()
or
WHERE |||

This scenario works fine in development mode for the customer.

I was able to reproduce the problem the customer was experiencing and also reproduce a memory leak issue that I am also working on (CR 201638).

I am able to run my sample application a total of 33 times in development, but only managed to get it to run 3 times as a deployed PCode executable.

This was tested against build 565 of PowerBuilder 6.5 on Solaris 2.6 also using Stronghold Web Server (Apache)

This exhibits similar symptoms of memory loss when the component simply creates and destoys a datastore on a component on Microsoft Transaction Server. The memory does not appear to be released until PB itself is shut down.

My results of memory usage when running the sample under NT 4.0 are as follows:

Initial 77068K
Start PB 81972K
Start App 82144K
1st run 83340K
2nd run 83480K
3rd run 83524K
Close App 83440K
Close PB 77068K

change the raise % from 5 % to 10 % and then changed it back to 5 %

the error item does not pass validation appears.

The solution is to change the static value .05 to .06 as shown below

SELECT "DBA"."employee"."emp_fname",
"DBA"."employee"."emp_lname",
"DBA"."employee"."birth_date",
"DBA"."employee"."salary",
"DBA"."employee"."ss_number",
"DBA"."employee"."emp_id",
"DBA"."employee"."dept_id",
"DBA"."department"."dept_name",.06
FROM "DBA"."employee",
"DBA"."department"
WHERE ( "DBA"."employee"."dept_id" = "DBA"."department"."dept_id" ) and
( ( "DBA"."department"."dept_id" = :deptid ) )

And then to change the data values from .06, .1, .15, .20 etc to 0.06, 0.10, 0.20 etc.

When creating a profile using Sybase Central it places information in both trees.

It is a problem because the profile does not show up when selecting Tools, Connection Profiles.

Open the HTML DW sample provided with EA Studio
Click on Scott to open manager details
Notice that the phone field contains a client side formatting of (617) 555-3246
click on the phone number
Notice that it changes to 6175553246
Click it again
Notice that it changes to (617) 555-3246
Now make a change to it and tab off the field
Notice that the phone number is now messed up and if the update button is pressed it fails.

This happens most often when the data for a particular row is beyond the 1 page limit of the datawindow for a single detail row.

Workaround: Assign the style sheet from within Powersite instead of PowerBuilder.

The call::super statement crashes in machine code when the event is a user event that returns a string parameter,
it does not crash with a long return value.

The same crash oocurs when the ancestor script of the user event is not overridden and both ancestor and descendant have script in the event.

Workarounds :

- Override the ancestor script
- Do not write any code in the descendant event but e.g. use an ancestor instance variable
- Override ancestor script and call the ancestor using the new syntax (without the Call keyword), for example :
string s
s = super:: event get_string()

integer li_row

dw_1.settransobject(sqlca)
dw_1.Object.DataWindow.Retrieve.AsNeeded='yes'
dw_1.retrieve()
li_row = dw_1.insertrow(1)
dw_1.deleterow(li_row)

Per development, this is not a bug. In DW expressions, '.' must be used as the decimal place.

The default datawindow layout setting restored ON STARTUP of the datawindow painter IF THE REGISTRY KEY
HKEY_CURRENT_USER\Software\Sybase\Powerbuilder\7.0\Layout\Default\Datawindow is missing has the View/Preview [p] using a shortcut of 'p' - it should have no shortcut. When the datawindow is fully previewed, the View menu is disabled and the user is unable to type a "P" anywhere in the datawindow painter at this point.

NOTE: If the user goes to Design/Options/Layout 'tab' and clicks on the "Default" button to restore the default layout in the datawindow painter, it DOES NOT make View/Preview with a 'p' shortcut. There seems to be some leftover beta initialization code that puts the View/Preview[p] on startup if it doesn't find the 'datawindow' layout key. When the user actually uses the product to set the default in the painter, no shortcut is created and the painter works OK.

Super::Clipboard("Employee Data")

The Super pronoun points to the system function version of the Clipboard function instead of using the DataWindow version. The DataWindow version of Clipboard, documented in Syntax 2, is only applicable to graphs.

WORKAROUND 1: use the Copy() function instead. I believe this is a documentation error, and the clipboard function would not be expected to work as documented, but development will make final determination.

WORKAROUND 2: Define a new function eg. wf_clipboard (string a_clipdata) and in the function just call the
clipboard(a_clipdata) function. In the datawindow event call wf_clipboard("string to paste to clipboard").

In particular with a font escapement of 900 (vertical text) the enhancement is
to have the border positioned properly around the text.

Typing in some characters (the number of characters must be smaller than the length of the mask in either the window control or the datawindow string column) causes pb 7 to add spaces to fill out the column when the user TABs off the datawindow column or editmask control.. .

In PB 6.5 no spaces are added.

Possible Workaround:
Use the trim() function to remove leading and trailing spaces from a string.

Fixed in 7.0.2 ebf codeline (build 8014)

This is an extremely large window with many datawindows and tab controls. The root cause of the problem has not yet been isolated. No other similar cases have been reported to date.

NOTE: In 5.0.04, 6.0, 6.5+ and 7.0, orientation 'sort of' works in that it lists Default, Portrait and Landscape but there is also a blank row at the end of the list so even Orientation is messed up.

<HTML>
<!--SCRIPT PSOBJMOD=TRUE
import( site.GetRootDocument().location + "/ObjMod.ssc" );
session.active = true;
InitObjects(session);
-->
<!--SCRIPT
myString = new String "Hello world, hello";
sampleString=myString.substring(5,11);
document.WriteLn("sampleString="+sampleString);
-->
</HTML>

Produces
Warning: undefined variable myString.substring[substring]

This is because in the objmod.ssc there is a

function String(x)
{
return (x)
}

When in a script an Autoinstiated UserObject is assigned to an any instance variable for the second time,
the class of the ANY variable errornously changes to type "string".

This does not happen in an identical situation when the ANY variable is a local variable.

Workarounds :
- use a PowerObject instead of an ANY variable
- set the ANY variable to NULL before the assignment

Workaround:
Connect with O73 driver

NOT A BUG:
Per development:
Error in the design of the user's DataWindow -- when InfoMaker constructs a Form, it creates a DataWindow with a fixed-height Detail Band, with a height larger than the page. The DataWindow looks for this configuration to identify an IM Form. In 6.5+ we had to formalize the Form definition as being Fixed-Height. In 5.0 it did not matter but, with the LiveScrolling enhancements of 6.5+, we needed the additional condition. Somehow the DW in the test suite has been given an erroneous AutoSizeHeight property on its Detail Band -- probably through manipulations in PB. Turn this flag off and the DW once again behaves like an IM Form.

NOTE: this will be the case for any datawindow, whether created in Infomaker or PowerBuilder. If the detail band
is larger than the "page" (which in the case of display on a window means the datawindow control itself) then you must turn AutosizeHeight off in order to have the scrolling work the way the customer wants.

See CR 199826 for more details.

Additionally, closing the find dialog via the X in the upper right corner closes the window, but doesn't give focus back to PowerBuilder rendering PowerBuilder development environment inaccessible. The Powerbuilder development environment is in a weird state where it doesn't even show up on the taskbar and you can't do work or get out of PB without killing it from the task manager.

If a user creates a custom FORM style and calls it "My Form" and associates it in the "Paper Size" attribute, it will get a relative position.

Default
Letter 8 1/2 x 11 in
Letter small 8 1/2 x 11 in
Legal 8 1/2 x 14 in
Executive 7 1/4 x 10 1/2 in
A4 210 x 297 mm
My Form

This is at position 7. But on another machine, there may be multiple other user-defined forms so "My Form" might be number 11 in the form and this causes a problem. Saving a setting as for example 8.5 x 11 in one printer driver (relative position 1) might translate to 11 x 19 inches in another driver (relative position 1).

Workaround: Get the current form list from the HKEY_LOCAL_MACHINE registry setting:

// This example creates the list of Forms in the numeric order. How the user can manipulate this with
// Modify() on each desktop can be tricky but is doable.

string ls_valuearray[]
long ubound,i

RegistryValues("HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Print\Forms",&
ls_valuearray)

ubound = upperbound(ls_valuearray)
FOR i=1 TO ubound
lb_1.additem(ls_valuearray[i])
NEXT

Also reference Microsoft Articles:
Q157172 - How to Create Custom Forms in Windows NT 4.0
Q183693 - Cannot Choose Custom Forms on HP III and HP 4 Family Printers

Workaround: Use Pcode

OLE Control with the DisplayType of Icon, loses previous updates when activated again.

Action: OLE control activates object MSWord97.
Type some text into the Word doc, Save in Word (first update). Do this twice more.
Exit Word Application.
Doubleclick on OLE control to activate the same doc.
Notice that only the first update is displayed and the others lost:

OS: Win98, NT4
PB6.0 Result Broken
PB6.5 Result Broken
PB6.5.1 Result Broken
PB6.5.1 Build 1067 Result Broken
Error: OLE Control with the DisplayType of Icon, retains only first update and loses all others when activated again.

PB7.0 Result OK

This happens in the datawindow painter and runtime.

Workaround:
Dynamically modify the SpinRange at execution time ie dw_1.object.COLUMNNAME.Editmask.SpinRange="-10~~~~-1"

OS:Any
PB6.x, 7.x : Feature does not exist

For example: The VariableDefinition object has information about:
-The variable's name and type
-Whether the variable is a scalar or an array and information about the array
-The variable's initial value, whether the value overrides an ancestor's value, and whether the variable is a constant
-The read and write access levels for the variable
-The scope of the variable (global, shared, instance, local, argument), including whether the variable is an argument and how the argument is passed

Using ODBC to SQL Anywhere works fine. The connection is using SQLCA and the code is doing an explicit disconnect after retrieval in script.

Workaround: Commenting out the "Disconnect using SQLCA" in script gets rid of the error but also does not use the transpool correct as it continues to create connections up to the maximum limit of the transpool. At this point, the user gets an error "Transpool limit exceeded". There is no "reuse" of connections and the connections stay open.

9/17/99 Fixed by Development: Also, in order for the fix to work, you have to set dbparm ThreadSafe=1

However, if you run PowerSite again, you will see that the file was actually created.

To workaround to crash, use one of the File wizards to create an HTML page, then edit the page and insert a Web DW, by choosing Insert->ActiveX->Design Time->Sybase HTML DataWindow DTC

OS:Win98,NT4

a)
Action:
With Menu object:
Define a Submenu Item:
Assign a bmp file which has a path and filename length longer than 63 chars to property ToolbarItemName.
Result: PB 7.x will GPF.

Workaround: Use the native MSS driver to create datawindows.

two possible workarounds:
1. insert the graph dw into a comosite dw.
- then saveas() and saveas('d:\d_gr.wmf',WMF!,FALSE) syntax work fine.
2. use the following script:
ret = dw_1.saveas('d_gr',WMF!,FALSE)
ret = dw_1.saveas()
- then you can save the graph with the saveas dialog as WMF

Workaround:
It is possible to use the POST method using the Powersocket 2.1 library which is not FREEWARE.
This has to be purchased seperately.

After a user has selected a printer in the PrintSetUp function, then a different printer
can no longer be selected dynamically in script using either the method described in
TechDoc 47627 or through an external utility.

In 7.0 we now have an
icon called AppIcon!, which does the same as Application! and no icon specified is translated to this icon. AppIcon! is selectable from the list in
the window painter and no icon is now translated to this solving both this problem and the name conflict issue. The performance degradation was caused because we were searching the library list for icon of the name "".

If you set up a cluster of Jaguar servers to take advantage of high availability etc. then you will run into issues if the Jaguar server on port 9000 goes down.

WorkAround: Write your own script instead that references the PowerDynamo object model with:
java.CreateComponent("mycomp","iiop://localhost:9000;iiop://localhost:10000;...")

But our "Datawindow Programmer's Guide" in Chapter 3 section "Providing query ability to users" :
"Limitations
You cannot use query mode in a DataWindow object whose data source you have modified syntactically (as opposed to graphically) and that contains the UNION keyword or nested SELECT statements"

And this is not correct according to CR149163. The "Limitations" should be replaced by :
"Limitations
You cannot use query mode in a DataWindow object whose data source that contains the UNION keyword or nested SELECT statements"

Workaround: Set TabStop in script: mle_1.TabStop[1] = 10
mle_1.TabStop[2] = 15
etc.

DO NOT set any tabs in the painter.

The shared datastores/datawindows become unlinked when a GetFullState() is done on a non-shared ds/dw object and a SetFullState() done on one shared ds/dw object.

The latter should cause the synchronization of all the shared ds/dw objects. This synchronization feature is
broken.

DUPLICATE BUG: See 205128 for current information.

WORKAROUND: use a script variable to pass the value instead.

There were several bugs in 7.0 in the dialog.
CR204215-dialog is modal (fixed 7.0 7015). Users could not "type behind" dialog to fix script like most replace dialogs. CR204215 fixed the modality but broke the ability to use the tab keys and hotkeys in the dialog.
CR205273- Broken tab and hotkeys in the dialog. Fixed in 8.0 but not in the 7.0 ebf line yet as of 2/9/2000.

Workaround is to add SetRedraw(true) and the display is then refreshed, but this was not necessary using 6.5.

I also migrated my altered test case back onto NT, where it is still running happily after over 2 million iterations with no sign of a memory leak.

Function GetFullState is not releasing memory after application is terminated on 2 tier application i.e. PB with ASA.

However, when you try to use the dw object in a WebDW component, no rows are returned.

use the latest OC on 11.1.1 will solve the problem

The problem described in this CR does not happen for either of the following:
-if there have been no new inserted saved rows affecting the datastore/datawindow.
-for datawindow to another datawindow

Per Development:
This is not a bug.

workaround:
type first the month and then the days

In pb 7.0.01 you just see:
{set str2 " "}{set str1 " " }

Worked ok in PB 7.0 (build 5031) and pb 5.0.04.

Datawindow Painter will crash with Crosstab datawindow when adjusting band size if 'Preview' view & 'Design' views are both open and 2 rows have been selected in the crosstab definition.

Build 7015 -> 0x10695e95 referenced memory at 0x00000004 - Memory could not be read
Build 6012 -> 0x10695d15 referenced memory at 0x00000004 - Memory could not be read

Workaround is to close 'Preview' view before moving any band in the 'Design' view

Engineering note: DW Runtime problem
I can recreate the GPF using the following syntax at runtime:
dw_1.modify("datawindow.header[2].height='132'")

Workaround: Using Round() function on computed field works ok.
exapmle: round(column_name) instead of only column_name in the computed field

Failed on creation from object context: CoCreateInstance (Package: IIS-{Default Web Site//Root/41051303Ssite}) (ProgId: ie.uo_testcrash1.1) (CLSID: {4C9410D3-977D-11D3-90F9-00A0C9ED4BAC}) (Microsoft Transaction Server Internals Information: File: d:\viper\src\runtime\context\ccontext.cpp, Line: 1292)

When trying to call the com object thru asp in a browser, the following error message also appeared:
error 'ASP 0115'

Unexpected error

/41051303Ssite/testcrash1.asp

A trappable error occurred in an external object. The script cannot continue running. -2147418113 007~ASP 0115~Unexpected
error~A trappable error occurred in an external object. The script cannot continue running. Server objectCreate Object
Successful
424 Object required Microsoft VBScript runtime errorof_testcrash1:

This happens with both external and non-external datawindows. Date colums with an editmask of mm/dd/yyyy do not exhibit problem.

** The error message actually indicates a generic problem that will be encountered anytime a user will try to implement an existing Jaguar interface. SO this issue needs to be addressed ASAP. **

Delete the DTC and readd it
Select a pbl and dw
Before switching to any other tabs attempt to close it and notice that it does not let you.

Notice that the difference here is that the Jaguar tab was selected previously. This is an inconsistency.

WorkAround:

Add a new record before calling the CreatFrom function:

loo_ADOrecordset.Movelast()
loo_ADOrecordset.AddNew()

Problem happens in Netscape and with Internet Explorer.

and autocommit=false, running the following script will execute incorrect
return codes:

ls_string = "Begin Transaction"
execute immediate :ls_string using sqlca;
dw_1.update()
commit using sqlca;

The update() returns a successful return code. The sqlca.sqlcode and sqlca.sqldbcode
return 0 after the execute statement and commit statement although the database
does not get updated.

ls_string = "Begin Transaction"
execute immediate :ls_string using sqlca;
dw_1.update()
commit using sqlca;

Using sqlsrv32.dll version 3.60.0319. Works ok with syc, mss and ASA.

Workaround:
Convert to syntax mode and replace the syntax with:
SELECT t.tid, t.somecols, u.uuid, u.somecols, v.vid, v.somecols, w.wid,w.somecols
FROM {oj {oj t LEFT OUTER JOIN u ON t.tid = u.tid
LEFT OUTER JOIN v ON u.uuid = v.uuid}
LEFT OUTER JOIN w ON t.tid = w.tid}

Per Development:
Not to be fixed. Easy workaround.
A portable datawindow that behaves identically against both ASA 6.x and SQL Server 7.0 can be easily created if the customer converts to syntax mode and uses the following select statement that is compatible with ASA 6.0, SQL Server 7.0 and DB2/CS:
SELECT t.tid, t.somecols, u.uuid, u.somecols, v.vid, v.somecols, w.wid, w.somecols
FROM {oj t LEFT OUTER JOIN u ON t.tid = u.tid
LEFT OUTER JOIN v ON u.uuid = v.uuid
LEFT OUTER JOIN w ON t.tid = w.tid}
Enhancing the SQL Painter to generate this SQL graphically won't happen anytime soon, so use syntax mode in datawindow painter. This works and lets the customer create a datawindow portable across several DBMSs.

Class Variables
Check to include global and instance variables that are in scope.

Happens only when creating an exe and no pbd's or dll's are checked off.

From Development:
In PB5, we had a major hole in the product. This hole was that we allowed people to make function calls using the dynamic keyword all over the place in terms of protected and private functions. There was not any checking done at all in PB5 to see what the accessibility of the function being called was.

In PB6, we closed this gap... and in doing so we have eliminated the ability to call a protected function from outside of the class it is declared in, or from one of its descendants or nested classes.

In looking at the documentation for PB7, I see that we document protected to include only descendants of the class where the function is declared. It also happens that we allow nested classes to call a protected function as well (this was the fix you mentioned in your bug description (CR 170917)). The idea is that a nested class should have access to anything that it's parent has access to.

In the case that this bug, 206805, was reported against, you have a UO (uo_button) that is dropped onto a window. The UO happens to contain the CB control and because of this, the Window Painter creates a CommandButton control on the window that inherits from the UO. If you export the syntax for the window w_genapp_sheet you will see that. This makes the UO class, where the script containing the function call lives, not allowed to call the protected function because it is not in either a nested class or a descendant class. The actual command button that is placed directly on a window, containing the same script, happens to be a nested class and therefore it is allowed to call the protected function.

The bottom line here is that it is actually a feature that we don't allow this. It is unfortunate that the hole in PB5 it was relied on by this customer. In addition, the fix to this would be an architectural nightmare and as a result we are very reluctant to go down that path without a very good reason to do so. If we were to do this it would definitely require major testing efforts and probably only be allowed to be fixed in a major release, or a specially tested EBF or something (if there is such a thing!).

I apologize that I don't have better news. I agreed that this looked like it should work, until I saw what is actually created underneath. Enforcing the protection laws of OO is what dominates this decision and if you check most other OO languages, they also would not allow this. It is unfortunate that we ever allowed this in the first place.

ALSO NOTE: In another customer test case, the UO was an SLE. Customer found that by putting the code on the SLE in the window, and choosing the option to Override the ancestor script. This makes that particular script behave as if the ancestor does not exist. That means that it acts as a nested class on the window, and then the function call works.

Workaround: If experiencing problems do not maximize painters.

Add a link to the link field for a web datawindow and then delete the link. Link = "" is left in the source which generates a hyperlink when the web datawindow is generated. Must export and delete.

The problem with this application is the error does not occur in the same place consistently. Basically adding records and deleting records from one particular dw. Sometimes it takes a few minutes of using the app, other times it happens immediately. Sometimes it does not happen until the app is closed or closed and then either try to open an object like a window (in development) or re-run the application.
The only consistency is the module & address where the error occurs.

I also ran with the PB Intersolv OEM 3.11 32-bit INFORMIX ODBC driver connecting to informix and never got an error.
Also tried with ASA database and MS SQL Server via MSS, still no errors.

To prevent the GPF, set a value greater than zero.
PowerBuilder's default timeout interval value is 300,000 milliseconds(5 minutes).

If a column in a dw has an edit style of dddw and that dw is (as described above), and you click on the column with the edit style dddw, that's when the error will occur. The error: Page Fault PBVM70.DLL@1037:11239c15 (using 7.0.01).
If the name is changed in the dw (in the one that is the dddw), to something else like description, the error will not occur.

This was not a problem in 6.5

The empty column is the result of the expression "1~t0" that gets saved for the value of the visible property.

Work-arounds :
- Export the datawindow and modify the expression to "0", i.e. remove the 1~t from the string
- Modify the datawindow column with the statement dw_x.modify("<column name>.visible=0")

m_main.Item[1].Visible = true
m_main.Item[2].Visible = false
m_main.Item[3].Visible = true
m_main.Item[4].Visible = true

When I run the window and the script on the command button gets executed I get the following results:

With 32 bit PB on WIN NT/WIN 95

Menu items 1, 3 and 4 are visible ---------> works as expected.

With 16 bit PB on WIN 3.11

Menu items 1, 2 and 4 are visible ---------> Regression, because it worked with PB 5.x

WORKAROUND:
string ls_select
ls_select=dw_1.describe ("datawindow.table.procedure")
dw_1.modify ("datawindow.table.select=''")
dw_1.reselectrow (dw_1.getrow())
dw_1.modify ("datawindow.table.procedure='"+ls_select+"'")

Happens on IE 4.0 and 5.0

dw_1.Object.DataWindow.Crosstab.Columns='Dept_name'
dw_1.Modify("Datawindow.Crosstab.Columns = 'Dept_name'")
dw_1.Object.DataWindow.Crosstab.Columns = ls_columns
dw_1.Modify("Datawindow.Crosstab.Columns = '" + ls_columns + "'")

Only workaround is to uncheck 'Rebuild columns at runtime' option in the datawindow painter but in many cases this will not be practical

This problem does not happen for External datawindows of type Grid or Freeform.

These 2 events are not triggered when vscrollbar or hscrollbar positions are altered with
a) click and drag mouse on the scrollbar itself
or
b) click on the arrow markers on each end of the scrollbar e.g. |<| |>|

Work-arounds :
- Call the RPC function with a string with a space in it instead of an empty string
- Check the argument within the stored procedure and modify the argument

Happens when tab order is greater than 0. Happens with n-up datawindows.
Happens under ie 4.0 and 5.0.

This happens when the Watch view is open in the debugger.

In the serv.log there is an Fatal Exception on GetRemoteVars of the component PBDebugger/PBDebugBroker

Development: No change to PB is required for this issue. A 7.0 enhancement caused a change in PATH requirements for PB to perform properly.

With PB7, we introduced a new feature that allowed users to associate BMPs and ICOs to their TOOLBAR items. With the addition of this feature,
at runtime we added the lookup and resolving of these BMP file. When BMP files are referenced but not found, PB does a search for them and it's often worse on a network. This happens every time a sheet is opened that contains a menu with a BMP (missing or not)

When the application is loaded, PB tries to locate each of the missing BMP files in the search path and in the EXE. This takes time and this occurs each time you call OpenSheet. PB goes out and looks for the same BMP files each time OpenSheet is called since the runtime has no way of knowing the BMP, ICO files will be there or not.

Resolution:

Adding the BMP files necessary to the PATH or as a resource to an application EXE file will cause a 7.0 application to perform the same as PB6 does without the BMP files available. This is because PB6 doesn't attempt to load these BMP files and when they are not found, it simply set them to the NotFound! stock icon.

For PFC users:
The typical missing icons are in m_master under View and Help. Most of the icons/bitmaps used are stock icons and are not a problem. If you deploy a PFC app and either forget to create a .pbr file or deploy these icons, PB will search for them (and fail) an sheet open performance will be worse if on the network or with a large path or multiple network drives in the path.

Large icons - largeico.bmp
Small Icons - smallico.bmp
List - listv.bmp
Details - detailv.bmp
Help Topics - helptop.bmp

The other option is to go to stock icons.

Build 7.0.1.7017 -> 0x010697a4c at 0x04dc06b8 memory could not be read (pbdwe70.dll)

11/8/99 -Develop'ers comments:
=========================
Tested here with service pack 3 on server. The update works with retrieve as needed on. So apparently
somewhere in between 6.50 and service pack 3 a locking bug was fixed. Then the bug was reintroduced in 7.0 and it is not known at this time if there has been a service pack for 7.0 with this fix in it or not.
Need to follow-up with Microsoft for server fix.

Also reproduced error in custom visual classes and in menus

This will give a error:
Warning C0014 : Undefined variable: al_array
Error C0070 : Mixing array and non-array in assignment statement

Workaround:
1. save the empty event
2. add
long ll_array[]
3. save uo
4. add ll_array[] = al_array[]
5. save uo
close uo
Problem if you open the uo and compile the script two times the error comes up again.

Workaround:
If you've enabled the override edit propeties of a column in a PB 5 0.04 and you migrate the datawindow to PB 7.01
you have to enable the propeties again.

Workaround:
Set resize the font and the disable the "Equality Required" property and then save the dw.

Problem also happens with no breakpoints and you hit step in and then hit
step over. The arrow skips a line but that line does get process at the next line.

On WIN95 received the following:, "n70 caused an invalid page fault in module pbdwe70.dll at 015f:105bf8f6"
On NT 4.0 received: "The instruction at 0x105c0936 referenced memory at 0x00000008. The memory could not be read."

(Fixed in 7.0.02 build 8011 and above PBDWE70.DLL)

The html page gets created, but it is missing the title and the anchor link text so
that when it is viewed, the page is blank. Workaround is to add the html title
and anchor link text directly to the html file that got created.

Workaround is to add the html title and anchor link text directly to the html file that got created.

Another workaround is just to export the project object and add in the fields that are missing (that get stripped out). This seems to be the function, link text and page title.
$PBExportHeader$p_webpb.srj
GeneratorID:{DA7487C2-3843-11D2-B30F-00600825A521}GENBC00000073
L c:\test.pbl
O u_globals
FUNC:of_sendtext <-- ** This gets stripped out unless you add it manually
FILENAME:c:\inetpub\wwwroot\test.htm
PAGETITLE:Here is a Page Title <-- ** This gets stripped out unless you add it manually
PAGESTYLE:
METHOD:Post
LINKTEXT:Here is the Link Text <-- ** This gets stripped out unless you add it manually
INTERFACE:CGI
URLPATH:/cgi-shl
INIFILE:C:\WINNT\pbweb.ini
SECTION:10017

Per Development:

This is working correctly in PowerBuilder8. (tested build 8002) The edit style of the column should be an editmask with a mask defined as !!!!!!!!!!!!!!!!!!!!!! (all upper case) or ^^^^^^^^^^^^^^^^^^^^^^ (all lower case) and the Client Formatting property for the datawindow (on the HTML Generation tab of the datawindow painter) should be checked. If these things are done the upper/lower case mask will work.

For example, if the case property is "upper" and you change it to "Any" and save
the dw. Open the dw again and the property for that column still says "upper".

Workaround: Export the dw and modify the column property in the *.srd file.

WORKAROUND:
In order to create a new composite datawindow, you would have to reduce the number of datawindows included on the library path. For example, you could create a PBL with nothing but an application object. Select that as your current application. Then copy whichever datawindows you wish to reference in the composite datawindow into that PBL temporarily. Create the composite datawindow, and then you can copy it back into your large application.

1. If a developer wants to use a new project, there is no way of connecting to a
project, and building the .pbl files with the correct objects, without creating
the .pbl files first, and then adding the objects manually (which could be
several hundred within many pbl files).
2. there is no way of synchronising all pbl files and adding new objects,
without manually selecting objects in each .pbl file, then manually adding new
objects into many different .pbl files.
3. Also suprising, when an object is deleted, a synchronise shows an error,
instead of removing the object from the .pbl.

for (idx0=0 ; idx0 < 50 ; idx0++ ) {
fixed_doc_desc[idx0] = new Character( ); <------######INCORRECT SYNTAX#####
}
doc_fmt = new Character[5];
for (idx0=0 ; idx0 < 5 ; idx0++ ) {
doc_fmt[idx0] = new Character( ); <------#####INCORRECT SYNTAX#####
}
doc_content = new Blob( ); <------ #####INCORRECTSYNTAX#####
}

The datawindow SqlPreview event will show the sqlsyntax string to be empty values for column specifications e.g. :
SELECT , , FROM WHERE = '163'

For example type in "255" for the Color property expression of any dw band. It is ignored and disappears on regenerating the datawindow.
The same value for other properties such as Pen.color, text.color etc - passes validation and is ignored but not lost on regenerating the dw

Cust would like a more consistant behaviour.
Should either give a validation error or work as a string. If it passes validation it should not disappear on regenerating

Problem only happens if the client and server are on the same machine.
Works ok remotely and if you wait for a undetermine amount of time.

More visible in PowerBuilder 7.0 since the views allow the developer to resize the design and have it immediately reflected in the preview "view" in the development environment. This could only be achieved during runtime prior to 7.0.

WORKAROUND: WHEN WORKING ON A CROSSTAB REPORT IN THE DW PAINTER, DO NOT VIEW A LIVE PREVIEW OF THE REPORT IN ANOTHER PANEL OF THE PAINTER. Wait to preview the datawindow until after changes have been saved to the datawindow object and then INSTEAD of using the preview panel, click the Run/Preview Object button in the ToolBar to open and view the report.

04/25/2005:

This CR was reviewed and closed as part of the Quarterly CR Review process. It is "Not targeted for any future release".

Returning 0 in PB 6.5.1 (32bit), PB 7.0 and PB 4.0.07. Worked ok in 16 bit pb 4.0.07. The message
number of 1035 should be sending the windows message em_lineindex.

WORKAROUND:
If you switch from SQL Painter to the DW Painter and you got the message that the SELECT has been changed but you didn't changed it
then check in the SQL painter if computed columns are lost. If yes add the comupted columns again and save the dw.

2. The script below GPF :
decimal{2} ldc_Result
SetNull( ldc_Result )
ldc_Result /= 1.00

Per PB Engineering:

This is not a bug, it is how query mode works now. CR 169396 was a change to require the AcceptText or tab off the column to cause an acceptance of the string. This fixed a loop which could occur when we "automatically" accepted the text when switching modes (to query mode or from query mode).

Workaround:
Put at the end of the BeginDrag event setredraw(false)
Put at the end of the DragDrop event setredraw(true)
This prevents PB drawing in the meantime of the drag process.

Problem happens when connected to syc,o73,or8,o84,mss.

When connected to SYC and after all columns are deleted, if you close pb the following error
message appears:

Smart Heap Library
MEM_BAD_MEM_POOL

Work-around :
- em_1.GetData(<decimal Variable>)
- <double Variable> = double(em_1.text) (PB6.5.1 onwards)

Running this resulted in the following error "The instruction at '0x00000000f' referenced memory at '0x00000000f' The memory could not be read. Another time PB itself shut down without an error message.

Need to determine if this is a PB problem or a problem with the activex.

Per Development, this wasn't related to the TIBCO ActiveX:
This is a problem with the clicked event not cleaning up an object reference and a subsequent event is causing a crash.

When a component is deployed to jaguar, the following the property of
com.sybase.jaguar.component.thread.safe
is missing from the all properties tab.

You cannot change the concurrency property unless this property is out there.

In the Jaguar CTS Programmer's Guide on page 81, if sharing and bind
thread options are selected, the concurrency option is implicity disabled.

Workaround. Put a comment in the double clicked event of the datawindow

When you update or insert in the dw painter and you double click on the
db blob column, mspaint will appear. Once you add or change the image
and then select file/update id in mspaint and then select save in the dw and
re-retrieve, the image is not saved to the table.

Workaround:
Set Bindupdate and Bindselect to "NO"

"Out of memory"
PB 70.exe - Fatal Application
Insufficient memory to continue

WORKAOURND: If you save the datawindow before making any changes the problem does not occur.

In PB 6.5.1 the correct length is returned and the column is not padded with spaces.

Workaround:
Problem is that you are not able to check with gettext() if a column is null or not. You have to use isnull(dw_1.object.<columname>[row]) to check if a column is NULL or not.

Workaround: RELOAD the psr after printing.

This can cause enormous performance problems on retrievals. This is not database specific and was found in ODBC, SYC and MSS drivers.

CR200800 was fixed for single numeric (INTEGER) retrieval arguments but not for NUMBER ARRAYS.

Fixed in 6.5 1127 and above.

Workaround: Set Display to Small Fonts.

For example in PB, '#' mask character signifies character can only be numeric values [0-9]

The registryget function is trying to retrieve a reg_dword using a valuetype of regstring!
and a valuevariable of string.

On win95 machine, the following error occurs:
pb70 caused an invalud page fault in pbvm70.dll at 0137:1133dc6e

On nt, app crashes. PB doesn't crash when using a valuetype of regstring!
and a valuevariable of ulong. (See testcase).

These bands exist in a datawindow:
Header
Detail
Summary
Footer

At this time only the Detail band has the Autosize Height feature.
____________________

This GPF occurs only for Pb6.x versions and not for PB7.x.

Workaround is to set up a new toolbar item that executes Format->Cells->Currency, which does work.

Workaround: Manually create styles instead of merging them from another spreadsheet.

Problem happens when the server pbl is on unix and the client on nt AND
when the client is on unix and the server is on nt.

Problem happens using the o84 and syd driver so it doesn't appear to be
db specific.

The symptom would be later in preview of the parent report or in the application, the user would be prompted for retrieval arguments (from the nested report) since the nested reports retrieval argument is no longer tied to the parent.

Workaround:
a) use the "COM Generator" rather than the old style "OLE automation" style of project.
All development efforts are in the "COM Generator".
b) use PBDs instead of DLLs

This worked fine in build 1112.

Fixed around 6.5 build 1127 and 7.0 build 7022

If the nested report and the data contained in it is less than 32k units (32.765 inches), it prints fine.

Other related problems:
- the list of columns produced when assigning the "Display" or "Data" columns are duplicates
- if the column name is > 20 characters, garbage characters appear after the name in the "Display value" or "Data value" column list.

If year is specified without preceding zeros e.g. '999-mm-dd', then IsDate() evaluates correctly that this year value 999 is out of bounds.

You can improve the performance 50-60% by cutting down on the size of the pbodb70.ini.

Some suggestions:
- Cut down the size of the INI file. Only include the section(s) for the driver you are using.

There are some fixes in 7.0 build 8006 and above to improve performance in reading the .ini file.

The workaround is to assign the dataobject property to the datastore/datawindow before calling SetFullState.

6.5 build 444 and 6.5.1 build 620 work OK as does 7.0 GA but not 7.0.1 6012 and above. Resizing the datawindow control somewhat seems to fix the redraw issue but this was not necessary in earlier builds and is not a workaround if the window or datawindow control is not resizable by the user..

Disconnecting the transaction object (disconnect using sqlca;) will not free the connections unless the transaction object is destroyed.

Workaround:
// Shut off retrieve as needed and turn it back on before calling Retrieve()
// This frees the connection
dw_test.object.datawindow.retrieve.AsNeeded='No'
dw_test.object.datawindow.retrieve.AsNeeded='Yes'
dw_test.retrieve()

If you're using a class library, query the value first:

if string(dw_test.object.datawindow.retrieve.AsNeeded)='yes'
// Shut off retrieve as needed and turn it back on before calling Retrieve()
// This frees the connection
dw_test.object.datawindow.retrieve.AsNeeded='No'
dw_test.object.datawindow.retrieve.AsNeeded='Yes'
dw_test.retrieve()
end if

Window functions for scrolling a window vertical and horizontal. The functions should make it possible to ensure that the user is at the upper left corner of the window.

Add to the Global Search, ability to replace text and compile.

There is no way to use the PB structure painters (local or global) to add comments about each element in a structure. Having comments would in many cases be used to provide embedded documentation (like we can with most other things in PB) for users of the structure. Note: Comments can actually be in the source files for structures and the compiler handles them properly but the structure painters do not allow them.

Add a 'Default Checkout PBL' property to the application object. When the Library:Source:Checkout dialogue box opens, that library would be the one selected. This will save programmers many minutes navigating to a directory and library, which, for each application, is ALWAYS the same.

Support ByReference Variables in OCX Controls. Currently, you can call OCX functions and reference OCX Attributes when the OCX is placed on a window. However, PowerBuilder does not support OCX variables by reference. You can declare them to be ByRef, but they are in fact ByValue. You can prove this by calling a function in the OCX which updates a variable -- you can see the updated value in MS Access, for example, but not in PowerBuilder.

Need to have the pborca.lib and pborca.h files distributed for PowerBuilder 7.0.

Create a new SaveAs option called ExcelFormatted! This will save the report to Excel *and* format the spreadsheet to really look like the report.

In the Datawindows, text object have a transparent property, but static text has not got that property at window painter. Also you can not draw a line on the pictures , it always goes behind the objects. It is not like that at datawindows also... And Group box objects are not containers of the objects which are in the group boxes. They are only for radio buttons, or check boxes.They should be a container also.

PB should allow auto-retrive of DDDW selectability (on/off).

PB should allow for better drag and drop support in PB painters including: a) move/copy functions + events between objects b) expendable ancestor code window c) ancestry drill through when selecting scripts for debugging.

Workarounds:
Obviously a PBD application works ok.
Furthermore:
1.) For relational operations there is no type promotions ie. datatypeconversions (page 79. Powerscript Reference 1) Hence if you would convert both values to Double using Double() and than compare works fine.
2.) If there should be decimals compared, use the datatype of Decimal ie. Decimal cd_small = 0.005
Comparing the decimals also works fine.
3.) Double values are Numeric literals with a decimal point and explicit exponent ie. double cd_small = 5.0E-4 (see page 79 table).

Customer says it worked ok in pb 5.0.04.

The Oracle 8.1.5 now supports NON-Blocking mode so the support can be re-added to the PB 7.x codeline.

The support for ASYNC using the PBO84 driver is already implemented in Powerbuilder 8.0.

Workaround:
Use the Style Type "Editmask" instead of the default value "Edit" and select the date mask from the selections which comes up when pressing the > button to the right of the MASK field.

Workaround: Use diffent datavalues or use a 2 state checkbox to save wo different states.

Microsoft SQL Server 7.0
select a.au_lname from authors as a <- GPFs
select a.au_lname from dbo.authors as a <- works OK.

Sybase SQL Server 11.5
select a.au_lname from authors a <- GPFs
select a.au_lname from dbo.authors a <- OK

Since these datawindows are normally migrated, it's unreasonable to work around this by stripping off the dbo.

If you build a datawindow with the following select statement:

Select start_date, end_date, termination_date from employee

Only the 1st and 3rd columns will show all the edit styles of type "date". The second column "end_date" will not show any date edit styles the user has defined in the database.