A such problem, we give A suggestion: I have A, B two DDDW, user is then selected after chose A, B and choose A time will retrieve the data, choose B will also be in the same grid data window to retrieve data, can in this way, when users choose A, wait A second, if this is the user chose B, through B to retrieve the data, to retrieve the data by A this step is not performed, if the user didn't choose B, or through A to retrieve data, which could give A good solution, thank you!

CodePudding user response:

Cannot add a query button,,

CodePudding user response:

At the same time also should pass to refresh B, add A button to estimate the user can't accept, choose A, still have to point the button, some trouble ah

CodePudding user response:

If delay special slow, it is suggested that the start dw_grid retrieve all down, and then setfilter (" empty ")

And then in A and B itemchanged same function,
//pseudo code
If A<& gt;" "Bthen
Dw_grid. Setfilter ("?=A ")
Elseif B<& gt;" "Then
Dw_grid. Setfilter ("? B=")
end if

CodePudding user response:

This seems to be no good ah, only after taking A can retrieve the data...

CodePudding user response:

Don't know whether you are a dw or one dw plus two query dw, you didn't tell layout,
If DDDW is the same in dw, even if no data lines, insetrow then deleterow after the DDDW will retrieve the first,

CodePudding user response:

Layout is that the above is a freeform data, it is AB two DDDW, here is a grid data window, through the AB to retrieve the data in the grid

CodePudding user response:

.

CodePudding user response:

1 set an instance variable ib_bchanged=false
2 data refresh event grid. Retrieve, the timer (0), restore tag ib_bchanged=false

3 above is a freeform data itemchanged: if a value change to start the timer (1), the timer check ib_bchanged, if is false call data refresh event,
4 above is a freeform data itemchanged: if b value change, set ib_bchanged=true, call refresh event

CodePudding user response:

refer to the second floor zdwydj_1999 response:

also should pass to refresh B, add A button to estimate the user can't accept, choose A, still have to point the button, some trouble ha

Some wait a few seconds is not as good as button convenient intuitive,,,

Don't want to that would retrieve in the timer, dw itemchanged events inside the
The timer (0)
,,
The timer (N)

CodePudding user response:

Not equal to add a button, when the first choice in the DDDW, flush the contents of the second DDDW, when the user choice to end, in two DDDW to click the query button, display the query results

CodePudding user response:

Now this is what design? Know know you in helping users save operation steps, don't know, thought you in deceive people, a second, reflect the slow point, will never too late to choose the value of B

CodePudding user response:

Ha ha, now is really in deceive people...