Override QBE behavior?

[jerryb]

1. I use QBE throughout my program. The same Navigator Bar on all screens.

2. I have a Master/Detail form.

3. I would like to QBE my Detail. If my result does not match my Master record, I would like to retrieve the matching (Parent) Master record for it to be displayed (as well as the QBE Detail result).

4. I'm running out of screen real-estate and really don't want to put an additional(and confusing to the user) Query button on the screen.

Question A: Is there any way to do this without overriding the default QBE functioning?

Question B: Is there any way to "supplement" the QBE functioning?

Question C: If neither A or B is possible, is there a way to take over (override) the QBE internal functioning completely?

Thanks in Advance,

Jerry Brillowski
jerryb@airmail.net

 

[Marco Kalter]

I don't think I completely understand the question. How can a query in a detail dataset result in records that do not match the master dataset?

------------------
Marco Kalter
Allround Automations

 

[jerryb]

Thank you for your response. I guess the best way to describe a question about QBE is to pose it as a QBE (Question by Example!

I have Customer Data (Master) on the left side of the screen broken down into individual fields.

I have a list of Customer Orders (Detail) summarized in rows on the right side of the screen.

This complete screen (both sides) is the "start" screen for manipulating orders. They can use QBE on the left side of the screen to go to a specific customer. (The matching orders will automatically show on the right.)

However, while on this screen, they many times only have the Order Number. Therefore, I want them to be able to enter the Order Number in the row field on the right side of the screen. The Order Number may, or may not be for the current customer. If it is not for the the current customer, I would like the "left side" Customer Data to move to the correct matching customer for the Order that is retrieved on the right side.

I hope this explains my situation a little better. If it doesn't I will be glad to try again.

Thanks so much for your efforts in keeping up with all our questions.

JerryB

 

[Marco Kalter]

If you want to accomplish this, you probably can't use the standard Master/Detail feature. It requires that the orders are always in the context of a customer, and in your case it sometimes is the other way around. I think you need 2 independent datasets (customers and orders), that you explicitly synchronize in your application. When the user queries the orders and scrolls through the result set, lookup the matching customers. When the user queries the customers and scrolls through the result set, select the matching orders.

------------------
Marco Kalter
Allround Automations