Query.run() never returns accessible query

[csda1]

When you run a

Query.run(queryname)

the action is to return a query in the default browse for the table or set associated with the saved query queryname. If you use the silent version

Query.run_silent(queryname)

the query is still run as part of the default browse, but the default browse never appears. In either case, the query result is not available to another browse or form of the same table or set associated with the query.

Is there any way to force a saved query to run with the current form or browse without having to use the built in menu or toolbar operation?

The only solution I can determine is to run the saved query, take the filter and order expressions, and rerun it on the desired form. But that means running the query twice, something I'm not willing to do.

Anybody have any other suggestions?

Regards,

Ira J. Perlow
Computer Systems Design & Associates
[email protected]

[csda1]

RE: Query.run() never returns accessible query

One other item to mention.

When you run a saved query with the built-in toolbar or menu options (which does functionally work), in maximized or windowed modes of the form, the Control panel displays even if it is currently hidden. This happens even in the runtime version. Placing a Controlpanel hide in the form's activation event removes the control panel, but it's an annoying flash.

Hence, the search for an alternative method.

Regards,

Ira J. Perlow
Computer Systems Design & Associates
[email protected]

[Tom Cone Jr]

RE: Query.run() never returns accessible query

Assuming the current form or browse are based on the same table as the saved query, why wouldn't tbl.query_primary_put() do the trick?

--tom

[csda1]

RE: Query.run() never returns accessible query

Tom,

Thanks for the idea. I had assumed this instruction only set the query, not actually running it, so I neglected to read the details of it that says it actually runs the query, however.....

Unfortunately, when you run the query that way, it takes (Are you ready for this?) the filter expression and runs it as the order expression of the query (you can see this by doing a ctrl-I on the form and looking at the expressions for each).

Any other ideas?

Regards,

Ira J. Perlow
Computer Systems Design & Associates
[email protected]

[Michael Humby]

RE: Query.run() never returns accessible query

Ira,

Perhaps an over simplified suggestion and not what you are looking for.

I run lots of scripted queries from a drop down custom menu. I am sure that the same process runs a saved query.

Michael

[csda1]

RE: Query.run() never returns accessible query

Michael,

As I stated earlier, I used the Toolbar and Menu choices (on customized versions) to do this but the Control Panel pops up. Hiding the Control Panel again on the activate event of the form makes it look better, but still has an annoying flash of the control panel.

Regards,

Ira J. Perlow
Computer Systems Design & Associates
[email protected]

[Robert Picard]

RE: Query.run() never returns accessible query

Hi Ira

I am not sure if your problem is the same as mine was.

I wanted my QUERY attached to a specified form so I could see only the records queried when viewing the form and to retrieve the search count.

This is the script fragment I finally came up with after a lot of help from Mr. Rabins and others. It might point you in the direction you want.
---------
Q_filter = query_filter_get("S_Sele_perform_period")
Q_order = query_order_get("S_Sele_perform_period")

:B_sch_results:tables:teletrac.filter_expression = var->q_filter
:B_Sch_Results:Tables:Teletrac.order_expression = var->Q_order
:B_Sch_Results:Tables:Teletrac.Query()

------

Good luck
Robert

[csda1]

RE: Query.run() never returns accessible query

Robert,

As I said earlier;

The only solution I can determine is to run the saved query, take the filter and order expressions, and rerun it on the desired form. But that means running the query twice, something I'm not willing to do.

The code you present gets the filter and order expressions, then runs them on the current form. But this would be convoluted for the purposes of my application, and would actually require that it be run twice (which is what I wanted to avoid), but thanks for your input.

Regards,

Ira J. Perlow
Computer Systems Design & Associates
[email protected]

[whanigsberg]

RE: Query.run() never returns accessible query

Ira,

Check me on this. If the saved query exists, and has been run in the past, and is therefore by now probably stale, who says it must be run again. In other words, can't it just exist to hold filter and order expressions ready to be retrieved by using the code Robert supplied.

Thus, you would not have to run the query twice.

Notwithstanding the above, the procedure is--as you say--still rather involuted.

Bill

[csda1]

RE: Query.run() never returns accessible query

Bill,

The problem is that in order to not run the query twice, they must follow the following procedure;

1. Do a query by form (for this case anyway) on another form other than the desired final one for display
2. Save the query
3. Cancel the current query
4. Run a saved query on the display form via a run dialog I provide

I don't want to have 2 and 3 both there. The exit from a query by form has no event that can be captured (at least not in this particular application - There is a really complex way to do it with other apps) to run code to do other stuff that needs doing (like go to the display form).

Anyway, the code is real sloppy that I've tried so far. I'm still slugging at it, but it's fighting me every step of the way.

Regards,

Ira J. Perlow
Computer Systems Design & Associates
[email protected]

[Robert Picard]

RE: Query.run() never returns accessible query

Hi Ira


This fragment runs in a script where the user is prompted for values and then the saved search is run only once using the outlined procedure above. The form "B_sch_results" is loaded but not activated. When the Query is finished running the form is activated with the records filtered based on the query.

It only runs once. As long as I don't run a new query for the form the old Query remains active.

You must be trying something different from what I think you are.

Good luck

Robert

[csda1]

RE: Query.run() never returns accessible query

Bill,

Also, apparently (in A5V4 Build 230 anyway),

query_filter_get(queryname) returns the order expression
query_order_get(queryname) returns the filter expression

I wonder at which point the code reverses them?...Perhaps we're in a "singularity" where everything is backwards? :?)


Regards,

Ira J. Perlow
Computer Systems Design & Associates
[email protected]

[Robert Picard]

RE: Query.run() never returns accessible query

Hi Ira

Here is a more complete example.

The following form is active->"main_contact_form"

The script is called with a button, you are prompted for several variables then the following occurs.

-------
Q_filter = query_filter_get("S_Sele_perform_period")
Q_order = query_order_get("S_Sele_perform_period")

:B_sch_results:tables:teletrac.filter_expression = var->q_filter
:B_Sch_Results:Tables:Teletrac.order_expression = var->Q_order
:B_Sch_Results:Tables:Teletrac.Query()

:B_sch_results.activate()

-------

Hope this is clearer

Robert
:main_contact_form.hide()

[Robert Picard]

RE: Query.run() never returns accessible query

Hi Ira

This is clearer???

Sorry I goofed when pasting the script fragment.

It should read

:B_sch_results.activate()

:main_contact_form.hide()

Robert

[csda1]

RE: Query.run() never returns accessible query

To all,

I haven't had time to try this, but I wanted to add this to the thread in case someone else needed it. There is a new XBASIC method (documented in readme file) in version 4.01 and up that does what I needed (and hopefully works!) As it states in the readme;

formpointer.run_saved_query(C name)
The method runs the saved query in the current form and applies it to the current form.

Note that a saved query is an operation that can also be run using the query.run() method. The difference between using query.run() and formpointer.run_saved_query is that the former runs the query in a new session and does not apply the query to the current form window.

Regards,

Ira J. Perlow
Computer Systems Design & Associates
[email protected]