Let's say I have this data entry window where QBF would work just perfect if I only could get hold of the query before it's exequted and do a couple of modifications. Is that possible?

Or perhaps I could even get hold of the values in the controls and do some validation and modification before they're parsed and made into a query? Is that possible?

- Oystein -

Øystein Reigem, Humanities Information Technologies, Allégt 27, N-5007 Bergen, Norway. Tel: +47 55 58 32 42. Fax: +47 55 58 94 70. E-mail: [email protected]. Home tel/fax: +47 56 14 06 11.

Øystein,

To do that, you can use a combination of code and send_events to the QBF* series of events.

Personally, I would use stored procedures for each one of the QBF* events, and then replace the default Quickevents on the standard QBF menu with my own stored procedures.

The only downside to this is that you will need to have the values in the editline be brought up to date before executing the query, so if you're trying to run some things behind the scenes, this might not be exactly what you want.

-Scott Revelation

Scott,

Thank you for helping me with this.

To do that, you can use a combination of code and send_events to the QBF* series of events.

So you say that what I wanted is possible. Correct?

Personally, I would use stored procedures for each one of the QBF* events, and then replace the default Quickevents on the standard QBF menu with my own stored procedures.

But you also say that your choice would be to chuck out all the existing QBF functionality and program from scratch. Right?

Assuming that what wanted I is possible: I'm afraid I need more details. I can find neither properties nor events that gives me access to the query. I want to modify the query before it's executed.

Here's a very simple example of what I'd like to do: Normally, if one fills in criteria for two fields, one gets a two-part query with a Boolean AND. I want a Boolean OR instead.

(And now it is I have to anticipate your suggestions for workarounds, because I know of a few that are not acceptable. With the 6 hour time difference between Norway and the US discussions tend to take a long time to finish.

(So here goes:) I know that one can get OR by putting a semicolon at the start of one of the criteria. But my clients don't want to learn tricky stuff like that. (Btw - why does the 3.61 online help still say that this doesn't work!? Doesn't it always work? Have I just been lucky?)

Besides in this example I want OR always, so why should my clients have to bother with that semicolon every time?

I guess your suggestion now is to put the semicolon in automatically. This can be done with a QBFRUN handler that puts the semicolon in the field before forwarding the QBFRUN event. I admit it works for this simple example, but not for more complex scenarios.

So to summarize - I know there are workarounds, but I want to know if I can to do this by modifying the query that QBFRUN put together - before it's executed. Unless of course there is some other smart and general way of doing it that I haven't thought of.

- Oystein -

View this thread on the Works forum...