Script Help - assign value then skip field

[enstorms]

I have this code set on first field (field rules table lookup). I have passed in a value from a calling form that sets the value of "typefee_id" which is getting set. If the value of the field is "Camp", I want it to set the value of the next field (cost_basis) to "Included", and skip it going to the following field. As the code is showing here, the value does get set to "Included" and the cost_basis field is skipped and all is fine. But, of course, this isn't what I want because it happens no matter what. If I Uncomment the tabstop within the if..end if statement, the field momentarily gets set, then assigns my default value (from field rules) and the skip never happens. The cost_basis field is selected.
I tried putting this type code on the form's init event and the first field's activate() event and arrival event, but for some reason, the value of typefee_id isn't getting set until the first field actually has focus. So I have placed it on the first field's OnDepart event. Which would be fine if I could get it to work as "I think" it should. I'm having a time trying to figure out when these events fire and when values get set.
Any thoughts would be greatly appreciated.
Thanks.
Ernie

dim tbl as p
dim frm as p
frm = topparent.this
tbl = table.current()
if frm:typefee_id.value = 2 then     'Camp 
	tbl.cost_basis = "Included"
	frm:Cost_basis.refresh()
	'frm:Cost_basis.object.tabstop = .F.
end if
frm:Cost_basis.object.tabstop = .F.

[MoGrace]

Re: Script Help - assign value then skip field

The OnDepart event for the typefee_id field should work for this.

if this.value = 2 then   [COLOR="DarkSlateBlue"]'and it is numeric and not a character value right?[/COLOR]
   cost_basis.value = "Included"
   cost_basis.refresh()
   [COLOR="Red"]yournextfieldname[/COLOR].activate()
end if

If typefee_id <> 2 then the cursor should land in the cost_basis field next. And while you probably can mix table and form methods in the same script, it is probably not the best way to go. The table methods are for behind the scenes work, whereas the form methods mimic user interaction. Since you are wanting to control what is at the form level, form methods should be used.

If this works for you then you might want to change the field rules to allow it and omit the skip rule. You can keep the lookup rule but set it to Allow Any Value so it doesn't interfere with the script on this form.

[enstorms]

Re: Script Help - assign value then skip field

Robin,
Thanks for all the good advice. I'm still trying to learn this xbasic stuff. Really confused as to when to use form obj. and tbl obj. Was wondering about that. If you assign a value to a form object, it does actually place it in the buffer, correct?

[MoGrace]

Re: Script Help - assign value then skip field

If you assign it to the form's value it should display, but if you assign to the the table you will have to bring the value to the form's attention - is one way to look at it.

[enstorms]

Re: Script Help - assign value then skip field

Thanks, Robin.
Ernie