Hi

I must admit that I do not fully understand your description of the problem. Are you saying that data columns are not displaying but random clicks makes them become visible?

If so I guess at this being a graphics driver problem and that windows is not displaying the DW correctly.

Apart from that I have not got a clue.

Regards

David

If not a lot of work, I would suggest to rebuild the dddw from scratch, save yourself some time.

No, have never seen this myself.

HTH

Sorry for not describing things clearly.

I've a drop down datawindow (ddw_select_customer) with 4 columns, customername, customercode, customertype, customerarea.

I try to use this drop down datawindow in a data window (dw_customer) for a field customercode.  Now I set the following things in Edit Properties.

Style Type :   DropDownDW
DataWindow : ddw_select_customer
Display column : customername        [ Instead of all 4 columns, it shows only customername ]
Data Column: customercode             [ Instead of all 4 columns, it shows only customercode ]

Till now no issues.  Issues arises when I go for modification of the above data, particularly Display Column and Data Column.    These two columns got a combo box (drop down data window ?) which should list all the 4 columns from the selected drop down data window (ddw_select_customer).   

While setting those properties for the first time, no issues.  When I go there for re-checking, I could see only one column in the display Column and data column properties.

But by clicking some points, randomly, all 4 columns becomes visible.  Couldn't understand why this is happening suddenly.  

Got about 50 datawindows, built from scratch in 2017 R3.  Checked with around 10 datawindows all having this issue.  By making 2 or 3 clicks randomly in the datawindow, we could get all required fields in dddw.   So far no runtime issues.

Happiness Always
BKR Sivaprakash

Can you make a small sample application which reproduces the problem?

You can set some fixed data in the data properties of the dddw, so you don't have to make us create tables and insert data.

What do you mean with modification of particularly "display column" and "data column"?

A dddw only has one column listed in the DISPLAY field and only one column available in the DATA field on the EDIT tabpage of the DW Painter.

What I have done when I need multiple columns is to create a new computed column with whatever I need displayed. There is still one ONE column in the displayed set of columns that is the key column; i.e. the one connected to the DATA. When the user selects a row, the key value is used.

Or maybe I don't understand the issue....  :/

Later -

Olan

I'll try with images.  

1.  Drop Down Datawindow with 4 columns.

2.  Now using this dddw in another dw (dw_entry_purchase_header), for field Supplier.  In the Edit Properties, DataWindow column is set with ddw_account_name_sub_branch_province and Display Column billbranchname is being selected.    When I click the Display Column, it should list all 4 columns from the dddw.   Here it list only the (already) selected column, billbranchname in display column drop down list and accountsubname in data column drop down list.

This could be viewed in the below image.  Display Column displaying only one column , instead of all the 4 columns.

The Data column also displaying one one column instead of all the four columns.

Hope this explains the issue better.

Hi, maybe I know what's going wrong here, so please check on the following.

You say "

"

In my experience, lots of times when you copy stuff from one datawindow to another, the internal id's of the datawindow get mixed up.

Edit the source of the datawindow which fails and make sure the id=?? number corresponds with the order of appearance of your column in this section.

For example, if your edit the source code and it looks like this, the column= order of appearance, has to correspond with the id=//. After "table(" there's a list of "column=". The first corresponds to id=1, the second to id=2, etc.:

table(column=(type=decimal(0) update=yes updatewhereclause=yes name=message_id ...
column=(type=char(8) update=yes updatewhereclause=yes name=to_user_id ...
column=(type=char(8) update=yes updatewhereclause=yes name=from_user_id ...
column=(type=char(1000) update=yes updatewhereclause=yes name=message_summary ...
column=(type=char(32765) update=yes updatewhereclause=yes name=message_detail ...
column=(type=datetime update=yes updatewhereclause=yes name=date_raised ...
column=(type=char(1) update=yes updatewhereclause=yes name=read dbname="cs_user_messages.read" ) ...
column=(type=char(80) updatewhereclause=yes name=from_user_name dbname="cc_user.user_name" ) ...
retrieve="PBSELECT( VERSION(400) TABLE(NAME=~"cs_user_messages~" ) TABLE(NAME=~"cc_user~" ) ...

column(band=detail id=1 alignment="1" tabsequence=10 border="0" ... name=message_id
column(band=detail id=4 alignment="0" tabsequence=40 border="0" ... name=message_summary
column(band=detail id=5 alignment="0" tabsequence=50 border="0" ... name=message_detail
column(band=detail id=6 alignment="0" tabsequence=60 border="0" ... name=....
column(band=detail id=7 alignment="0" tabsequence=70 border="0" ... name=....
column(band=detail id=8 alignment="0" tabsequence=80 border="0" ... name=

You don't see a "column(.... id=2..." nor "column(...id=3)" in this sample, because those columns are not shown on my datawindow.

Personally I NEVER copy columns from one datawindow to another, or at least not without afterwards checking on all the column id's in the edited source code.

HIH

Ok, no.3 is clear now. :)
Can you export your datawindows and attach them?

Hello,

PB 2017 R3

Here is attached those two dws (drop down datawindow and entry datawindow) in the attached zip file.  You could just unzip and open the project.   ( all files are zipped and attached as rar file ).

dw_entry_purchase_header                  is the dw to check.

Check the edit properties of the field suppliername.

And also the edit properties of the field supplierbranchfk.

Both uses the same drop down datawindow, both showing different set of columns.

1. If we first check the edit properties of supplierbranchfk, then move to suppliername, NO issues. everything is ok.
2. If we first check the edit properties of suppliername, it lists only one column.
3. Once all columns are displayed, this issue re-appears only when we re-open the datawindow again after closing it.

Happiness Always
BKR Sivaprakash

I've been able to reproduce your problem, at first I couldn't ... so give me a moment to see what made it possible to reproduce the problem...

At first I could not reproduce the problem because I migrated to PB2019 R2 beta.

The problem only seems to exist in PB2017 R3.

I'll report this as a bug to Appeon.

I've attached your problem case with the problem narrowed down, leaving only the dw with the problem column.

If you:

1) click on the "suppliername" column which has a dddw in the edit style.

2) click on the properties "Edit" tabpage

3) scroll down to where the dddw display and data columns are, you'll only see 1 column listed

4) without changing from the tabpage "Edit", click on the other column,

5) click back on "suppliername" and voila! ... There are the other columns.

In pb2019 (R2 beta) this little problem doesn't seem to exist and I've compared the datawindows, absolutely nothing has changed due to migration. It's a difference in PB itself.

(see the attached case)

Dear Sivaprakash BKR,

I've reported this as bug 3557. I thought I'd save you the trouble of explaining everything again.

Regards.