Using a form as a lookup list not populating correctly

[spain246]

Here's the steps for my problem:

1. Login database with "Administrator" account. PW:password

2. When Main Menu Appears, select add or edit player.

3. When my Parentform/Embedded Browse appears, I select the player I want to edit and click the button "Open Player Info"

4. That opens my "Player Edit Info" screen.

Here's where the problem hits. It is calling up the incorrect player. If I close the "Player Edit Info" form, then select "Open Player Info", it displays the initial player I selected.

I've been working on this all day, and I just can't figure it out. (Or i'm just tired again). Can someone give me a suggestion as to why my edit screen won't open to the correct player the very first time?

Attached is a copy of my problem. I would greatly appreciate any help anybody can provide. I feel like the "variable" i'm using won't refresh for some reason.

Thanks in advance! (I'm slowly getting this!)
Steve Hall

[[email protected]]

Hi Steve

Whats you Password

[spain246]

The password is PASSWORD

Sorry! :-)

Steve Hall

[[email protected]]

Hi Steve

I have change a few things

Put in a zoom to record

and change the index that it was using to lname

and made sure that it is using that index through out each move and it seems to work.

Please install to a different directory

I could not update the members index "lname" as always in use!

Andy

[Tom Cone Jr]

Hello Steve & Andy.

I took a look to see if I could explain was going wrong with Steve's original script.

His approach uses xbasic to run a query against the table supporting the called form. The query uses the current value of the "link" column in browse object in the filter expression. He does it like this:

f = :Form.load("member", "dialog")
f:Tables:Members.filter_expression = "Link = '" +vPlay_Link +"'"
f:Tables:Members.order_expression = ""
f:Tables:Members.query()

He then shows the form and the wrong player is displayed. This was initially baffling because I could see no syntax errors in his script.

The answer is suggested by running the script twice. The player that had been previously selected shows up when the form is displayed the second time.

Here's the explanation:

The script runs against the table supporting the form, but never synchronizes the form with the table. The first query remains in effect when the form is displayed the second time. By running the script against the table supporting the form, the form itself doesn't "know" that the query occurred. This is easily remedied:

f = :Form.load("member", "dialog")
f:Tables:Members.filter_expression = "Link = '" +vPlay_Link +"'"
f:Tables:Members.order_expression = ""
f:Tables:Members.query()
[COLOR="Red"]f.resynch()[/COLOR]

Just resynch the form before showing it.

If you want to run the same query against the form itself (not the table supporting the form), you'd do it this way:

'	***** Load target form *****
f = :Form.load("member", "dialog")
'f:Tables:Members.filter_expression = "Link = '" +vPlay_Link +"'"
'f:Tables:Members.order_expression = ""
'f:Tables:Members.query()
'f.resynch()

[COLOR="Red"]f.queryrun("Members->link = '" + vPlay_link +"'","","","No","",.f.,"T")[/COLOR]

f.allow_change(.t.)
f.activate()
f.show()

Notice that since the query runs against the form directly, there's no need to resynch the display.

Hope this helps.

-- tom

[[email protected]]

hi Tom

thanks for the explanation

Andy

[spain246]

Thanks Andy and Tom for all of your help! That explains a whole lot!

Anybody have a good solid manual for this? :)

Steve Hall