Code Suggestion

[forskare]

I have an embedded browse on the parent form and need to open a form (EEI) and pass the account number. Using Tom Cone's code, I got the form to open but still need to pass the account number. Here's the modefied code on the button to open the EEI form:

if is_object("EEI") then
' EEI.new_record()

EEI:account_numbr.value=Browse1:acount_numbr.value

EEI:Localaccount_numbr.value=Browse1:account_numbr.value

EEI.show()
EEI.activate()

else
form.load("EEI")
'EEI.new_record()

Browse1:account_numbr.value=EEI:account_numbr.value

Browse1:Localaccount_numbr.value=EEI:account_numbr.value

EEI.show()
EEI.activate()
end if

What do I need to add or change to pass the account number?

Thanks,

kenn

[Tom Patten]

RE: Code Suggestion

Ken,

Are you (We) in luck. Tom Cone has posted three examples of doing what you want to do. See Code Archive - Passing Values between forms.

They are GREAT!

Thank you Tom.

Tom

[Tom Patten]

RE: Code Suggestion

PS Ken,

Place the accountnumber field from the browse on the form itself, make it hidden, then Tom's techniques should work as advertised. geeeeeeeeeeez they are neat.

tom

[forskare]

RE: Code Suggestion

Tom,

Yes, I agree. I used the 2nd method to open one form and pass the value. In this case, I trying a little different twist. I did as you suggested from the git go but the value is not passing. I'm trying out another thought so will see where that takes me.

Tom Cone's advice in response to my earlier post is very helpful as it's very easy to get objects mixed up with tables and forms.

kenn

[Tom Cone Jr]

RE: Code Suggestion

Ken, when you reference an object on a form, it's important to include a complete reference. Unless Browse1 is the name of your form, you've left the formname out of the reference for the object you're trying to manipulate.

It's like trying to furnish a path to a file, and omitting the drive specifier.

If your field is in a browse it probably should be referenced as:
formname:browse1:fieldname.value

Notice the colons.
They mark the path from form to the object in question.

Notice the one period.
It marks the property you seek to manipulate.


Personally I avoid this approach like the plague. Always worry that the user will have changed rows on me, inside the browse. Very much prefer to work with the form and not browses.

-- tom

[forskare]

RE: Code Suggestion

Hi Tom,

Ther reason for the browse is that it is read only, a reference, so to speak. I got it to work, at least it seems to be. I remembered that some guy by the name of Tom Cone told me that when you change the column name from case_numbr to case number it changes the reference. Once I changed that, it worked.

However, I am encountering a couple of cosmetic issues; one is a screen jump when the form loads and the other is a delayed reaction of the form loading after the button is pushed, anywhere form a couple of seconds to 5 seconds.

Going to play with it a bit and see what happens.

Thanks,

kenn

[Steve Dentler]

RE: Code Suggestion

Ken, I found your code confusing as in the upper section you were pasting values to the EEI form and in the lower section, you were pasting values elsewhere. Maybe try this if you are trying to pass values to the EEi form while the browse is open.

P = parentform:browse1.this
f = obj("EEi")
if is_object(f)
f.activate()
Sub1:
f.new_record()
f:localaccount_number.value = p:account_number.value
f:Localaccount_numbr.value = p:account_numbr.value
goto done
Else
f = form.view("EEi")
goto Sub1
end if

Done:
end