Go to master based on child info

[Louis Nickerson]

I have a form (customers) that is based on a set that is based on tblcustomers and tblinvoices. Data about the customer is on the main form and data about each invoice for that customer is contained in an embedded browse on the form.

I want the user to invoke an x-dialog box (from anywhere in the application and then enter an invoice number in a taxt field on the x-dialog.

Upon leaving the x-dialog I want the "Customers" form to open and goto the customer record AND highlight the appropriate invoice record in the embedded browse.

Any help would be most appreciated.

Thanks

Louis

[forskare]

RE: Go to master based on child info

Why not use the OnRowDblClick event of the browse? Musch quicker and easier for the user.

kenn

[Louis Nickerson]

RE: Go to master based on child info

In real life, a customer might (frequently does) call up and say " I have a question about my invoice.

The user taking the call might be knee deep in another area of the application.

I want the user to be able to press a hot key, type the invoice number and hit enter and be looking at the customer form with the desired invoice already highlighted.

Louis

[Tom Patten]

RE: Go to master based on child info

Louis,

I'd do the following:

InvNo = ui_get_text("Invoice Number","Enter the invoice number.")

Open Formname specially designed for this purpose, with index set for "invoice number") - Actually I'd reverse the set with Invoice 1:1 customer.

f=form.load("Formname")
f.index.set("InvoiceNumberIndex")
f.find(InvNo)
f.view()

To be accessible anywhere, if you have room and a common menu bar, why not place it on the menu bar.

Hope the above helps.

Tom

[forskare]

RE: Go to master based on child info

Ok, but how is the user going to know the invoice # if the customer doesn't have it?

kenn

[Louis Nickerson]

RE: Go to master based on child info

If the customer is calling with a question about the invoice they received, the are usually holding it in their hand.

[Louis Nickerson]

RE: Go to master based on child info

Tom,

Thank you for your suggestion, I'll give it a go.

Louis

[Tom Cone Jr]

RE: Go to master based on child info

Louis,

I like Tom P's approach, but I'd change the final line:

f=form.load("Formname")
f.index.set("InvoiceNumberIndex")
f.find(InvNo)
'f.view() 'I think this might open second instance of the form.
f.show() 'since form is loaded, just show it.
f.activate()

- tom c

[forskare]

RE: Go to master based on child info

usuaslly....but what if they lost it or it got thrown away or they're too lazy to go and get it. Picking up the phone and calling is a chore for some folk.

If the browse shows all invoices for the customer (it's a much higher probability a customer knows their name), double clicking on the row containing the invoice in question is less work that typing an invoice number and risking "some" chance of a miss type.

Oh well.........

kenn

[Louis Nickerson]

RE: Go to master based on child info

Ken,

Don't get me wrong, I truly appreciate your suggestions and you make alot of sense. I am trying to deliver specifically what the customer is asking for.

Realistically speaking, using your approach is a valid and likely solution. I have already implemented exactly what you suggested. However, what the customer wants, the customer gets, thus the need to navigate to the parent record based on the input of the invoice number.

Thanks again for your input.

Louis

[forskare]

RE: Go to master based on child info

Hi Louis,

Yes, you are so right. My comment of "Oh well" was out of line, I apologize.

kenn

[Louis Nickerson]

RE: Go to master based on child info

Ken

No offense taken...no apology necessary!

Louis

[whanigsberg]

RE: Go to master based on child info

Hello everyone,

I'd like to add a word in favor of Louis' original concept. After all, his user is accustomed to a particular form--header with embedded browse of individual invoices.

The proposed solution which is certainly practical takes the invoice number and does a find in an inverted set. But now the user will end up looking at a different form and what if he wants to review other invoices linked to the same client?

So if the user supplies us with the invoice number why don't we:
-use xbasic to look up which header it goes with;
-go to the invoice set (in which the header is parent);
-find the appropriate header;
-find the appropriate invoice in the embedded browse.

I don't see this a much more difficult than the alternative solution and it should appear more transparent and intuitive to the user.

Bill

[Louis Nickerson]

RE: Go to master based on child info

Bill, Thank You!

Could you please offer some direction?

Louis

[whanigsberg]

RE: Go to master based on child info

Well better late than ever, here is an example.

Since you are starting out with the number of the child record you must first find the parent and then fetch the child.

This code is on the single button of the sole form in the example.

Bill

'--------------------------------------------------
dim shared vClient as C 'shared so the values persist until next time
dim shared vInv as C
if vInv = "" 'give the variable a value if the application was just opened
vInv="01"
end if

'Get the desired invoice number
vInv = ui_get_text("Find an invoice","Enter invoice to search for:",vInv,"")

'make sure it is valid
if .not.exist(vInv,"link","invoice_no")
ui_msg_box("Wazzmaddawidya","Invoice "+vInv+" doesn't exist.")
end if

'Find number of the parent record by looking it up in the link table
vClient = lookupc("f",vInv,"client_no","link","invoice_no")

'make sure client number is the form's active index
parentform.Index_Set("client_no")

'Find the parent record
parentform.find(vClient)

'Now find the child record
t=table.current(2)
t.fetch_loc_next(vInv,"Invoice_No")
parentform:browse1.Resynch()
parentform:browse1.activate()

end