cherokee
19th November 2010, 16:47
Hello again,

I am trying to re-run the query.extension after a user selects if wants to see history or not but after I do execute(find.data) same data still display on the session... Is it possible the query.extension can be re-executed somewhere else besides the before.program?

Here is my code...

|****************************** form section ********

form.1:
before.form:
if not background then
if not history then
query.extension ="tdsls989.cmbc refers to tdsls041 "&
"and tdsls041.oqua <> tdsls041.dqua and "&
"(tdsls041.bqua <> 0 or tdsls041.dqua = 0)"
else
query.extension ="tdsls989.cmbc refers to tdsls041 "
endif
execute(find.data)
endif
|****************************** choice section ********
choice.user.2:
before.choice:
if history then
history = false
else
history = true
endif
to.form(1)

Thanks again.

BaanInOhio
19th November 2010, 17:14
Try 'rebuild.query'. It resends the updated query extension to the database, ready for a 'find.data' to utilize it. It can be used anywhere an 'execute(find.data)' can be used.


if not history then
query.extension ="tdsls989.cmbc refers to tdsls041 "&
"and tdsls041.oqua <> tdsls041.dqua and "&
"(tdsls041.bqua <> 0 or tdsls041.dqua = 0)"
else
query.extension ="tdsls989.cmbc refers to tdsls041 "
endif
rebuild.query()
execute(find.data)

cherokee
19th November 2010, 17:24
Yep... worked!!!

Thanks a lot!

mark_h
19th November 2010, 21:43
I thought rebuild.query did not work in 4c3 or 4c4?

BaanInOhio
20th November 2010, 00:19
I thought rebuild.query did not work in 4c3 or 4c4?

Works fine in 4c4. Probably depends on the portingset and version of the tools binaries. I found that a rather recent portingset/tools update at one client provided the "ftp.*" calls in 4c4. Now if I can locate good documentation on them...