I'm mixed up again

[Edward F. Schulz]

Hi Phorum,

On a form based on a 1-many set where the parent is members and the
child is dues (in an embedded browse). I have the following script on
the onkey event of the form.

if a_user.key.value = "{F3}"
a_user.key.handled=.t.
IF a_user.key.event = "down"
f=parentform.active()
if f="browse1" then
parentform:soc_sec.activate()
parentform.fetch_next()
else
Browse1.Activate()
browse1.new_record()
browse1:datepaid.activate()
end if
end if
end if

The intent of this script is to ease the monthly dues data to be entered. Each record gets 6 entries and more than 90% of the records, 4 of the 6 entries is the same. The button that brings up this form stores 4 variables for the ones that seldom change for a given month. What I expect of this script is for it to put focus on soc_sec in the parent form when it is entered. Next by presssing enter or
tab, it would enter the 4 variables appropriately in the child table, next the user would type in the other 2 fields. Then after pressing enter again it would place focus in the parent , fetch the next record and the process would be repeated. This seems easy enough to accomplish.

What it doesn't do is place focus on soc_sec in the parent when it is activated nor does it place focus on datepaid of the child table.

Maybe I am asking for miracles,
efs

[Stan Mathews]

RE: I'm mixed up again

Did you double check the properties for the form fields in question (sos_sec and datepaid)to make sure that these are the actual names of the form/browse fields. If multiple instances of the fields have been added and removed the names sometimes resemble soc_sec0, soc_sec1, etc. This would make more sense for the form field sos_sec than for the browse column.

[Edward F. Schulz]

RE: I'm mixed up again

Hi Stan,

Good points, but I just double checked and both fields are in tact and spelled right. BTW, this used to work and no changes have been made anywhere.
Thank you for your inquiry,
efs

[Tom Cone Jr]

RE: I'm mixed up again

Ed, I don't see anything wrong with your script. Why not post a working model here so we can see it in action? Please include step by step instructions on how to see the problem, along with a detailed description of what it is you want to happen instead.

-- tom

[Edward F. Schulz]

RE: I'm mixed up again

Hi Tom,

I have the bottom (else) part working now after a minor change. The
top part just won't put focus where I want it. I changed soc_sec to
nam_con_cat which is a table level calc field and is where I want the
focus to go when F3 is pressed. It looks like this now:

if a_user.key.value = "{F3}"
a_user.key.handled=.t.
IF a_user.key.event = "down"
f=parentform.active()
if f="browse1" then
parentform:nam_con_cat.activate()
parentform.fetch_next()
else
Browse1.Activate()
browse1.new_record()
browse1:datepaid.activate()
end if
end if
end if
I may not have done a very good job of explaining the intent of the
script. When the form is entered, focus should go on nam_con_cat which
will be the first member in the order. The previous form sets defaults
for 4 of the 6 fields to enter. I use sys_send_keys on the first field in the child to automatically enter the defaults previously defined. Next the
user eneters data in the remaining 2 fields, and presses F3, that is
supposed to shift to the parent table and place focus on nam_con_cat and fetch the next record in the order. This is the part that is not working now.

I'll try to pare it down in order to attach it here.

Many thanks for your help,
efs