go to record# function

[hov333]

Hi all,

I'm working on a form that allows the user to scan a worknumber which takes them to that record number. My old form did this by retrieving the record number and going to that record via lookup function.

This new form, includes the parent records on the top (ship to company, customer, etc). The idea is that you batch ship for each customer then move to the next customer. I'd like the functionality to stay the same but I cant get the lookup to work, the "go to record" function is focusing on the parent table. Is there a way to direct this function to the records in the child browse?

I've attached a screen shot for reference. Please let me know if I need to clarify anything.
ship.JPG

Thanks!

[Ray in Capetown]

Re: go to record# function

What's the relationship between the (what looks like) two browses on a form?
You say "scan a worknumber which takes them to that record number" in what table and which part of the form related to that?

Needs some clearer explanation of content tables in this snapshot, and then what you want to happen in that context.

Can you do that?

[natn1251]

Re: go to record# function

recno("mychildtbl") will return the record number of the record in the child table browse which has focus
Assign that value to a variable then pass it to your lookup function
dir rNbr as N
rNbr = recno("mychildtbl")

Hope that points you in the right direction

[john michaels]

Re: go to record# function

This new form, includes the parent records on the top (ship to company, customer, etc). The idea is that you batch ship for each customer then move to the next customer. I'd like the functionality to stay the same but I cant get the lookup to work, the "go to record" function is focusing on the parent table. Is there a way to direct this function to the records in the child browse?

No. The topparent.recno_goto(recordnumber) will only address the parent table. That question being able to be answered directly, and being said, I am not clear on what you are actually trying to do. You will need to be a bit more exacting/detailed in your description of what you want the action to be, for more help or a different solution.

[hov333]

Re: go to record# function

thanks for the replies guys. To clarify, the browse at the top is the parent (customer list). The browse below it is the items belonging to the customer. The worknum field is a variable which will allow the user to input the worknumber for the item and the browse will navigate to that item.

[Tom Henkel]

Re: go to record# function

Is this individual tables or is there some sort of set involved?

[hov333]

Re: go to record# function

Hi Tom, this form is designed on my set where the Customer table is the parent and the items is the child. I'm trying to figure out an alternative to topparent.recno_goto() to point to the desired record in my child table (embedded browse). Any suggestion?

[Tom Henkel]

Re: go to record# function

When you have the form open, is it "on" the parent record? When you scan the work number, does this bring you to the customer record?

If either of these is true, by the definition of a set, you should have the child items in the associated browse. Is that not happening?

Tom

[hov333]

Re: go to record# function

well the point is that the work number is a field in the child table which is where I want to be navigating, not at the parent level.

[john michaels]

Re: go to record# function

If you have the current parent in focus for the needed child records, the following will find the needed child record. This should work OK as long as the number of child records is not very large. Be sure to have the field names for the work number for the scan field and the child table work number field correct (in red in script). Also assure the field types and variable scopes are correct (character vs numeric). You can put this on a form button or maybe the field event for the scanned work number field.

'get the scanned work number
	dim vn_work_number as N
	vn_work_number=topparent.work_number.value

'loop through the child table evaluating the work number in the table with the scanned number
	dim valert as C=""
	dim tch as p
	tch=table.get("proj_prices")
	while .not. tch.fetch_eof()
		if tch.work_nbr=vn_work_number
			valert="Record found - "+ vn_work_number
			exit while
		end if
	tch.fetch_next()
	end while
	if valert=""
		valert="Record Number - "+vn_work_number+"  - not found"
	end if
		ui_modeless_dlg_box("Work Number",<<%dlg%
		{lf};
		{text=50valert};
		{lf};
		%dlg%)
		sleep(2)
		ui_modeless_dlg_close("Work Number")
	end if

[hov333]

Re: go to record# function

John, right now im scripting using a button. Is there a way to fire it when the user enters it into the "scan worknumber" type-in field? I don't want to put it on change of the field...

[Tim Kiebert]

Re: go to record# function

well the point is that the work number is a field in the child table which is where I want to be navigating, not at the parent level.

That maybe so but in a set based form you only have the child records available that belong to the parent record. So you have to first navigate (by find or query) to the correct parent then navigate within the resultant child records.

To repeat Tom Henkel's question. When you have the form open and you scan the worknumber are you already on the correct parent or do you want the search process to bring up the correct customer as well

John, right now im scripting using a button. Is there a way to fire it when the user enters it into the "scan worknumber" type-in field? I don't want to put it on change of the field...

How are you currently triggering the process in the 'old form'

[Mike Wilson]

Re: go to record# function

What I believe everyone is saying is that the ability to work with and address child records, the parent of that child must first be in focus. Then you can address the child records. This is what prompts Tim's (and Tom's) question..

When you have the form open and you scan the worknumber are you already on the correct parent or do you want the search process to bring up the correct customer as well.

John, right now im scripting using a button. Is there a way to fire it when the user enters it into the "scan worknumber" type-in field? I don't want to put it on change of the field...

I'm guessing this answers Tim's question on how you are currently doing it. Can it be done with a field rule field event? I don't have a scanner to test how an entry by scanner might work. Sorry. You might play with the table level field rules and see what you can make happen.

[Tom Henkel]

Re: go to record# function

We use scanners for our File Room Retrieval system as well as our Supply room. The scanners can be programmed with prefix and suffix characters to initiate an action in alpha such as a find.

Tom

[hov333]

Re: go to record# function

The customer (parent) will be initially selected by the user by clicking on the record in the browse at the top of the form. Once on this parent, the scanned number should navigate to the correct child via worknumber.

Tom, very interesting, I hadn't heard of this. Any particular scanner that you can recommend? Ours is a basic wireless scanner at the moment.