Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
One - many layout ??s
Message
 
À
07/01/1999 18:27:17
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Divers
Thread ID:
00173318
Message ID:
00174275
Vues:
33
Thanks, Trey - a good answer!

I only have one thing to add for Steve: In a grid, you need to put the double-click code into EACH Mygrid.ColumnN.TextBox control. If you put it into the GRID DblClick the TextBox controls will override it. If you wish the DblClick code on each column to be the same, then put it into a form method and in each DblClick method simply put: Thisform.MyDblClick()

HTH
Barbara

>[snip]
>
>As Barbara mentioned, you have a good start for the layout and her ideas were the same I would have suggested.
>
>>What construct would you suggest to accomplish the 'double click' taking you to correct item?
>>
>The DblClick code will have to go in the current control in the grid's column - another good reason to have minimal child info in the grid.
>You could either do something like:
>thisform.pageframe.ActivePage = 2 && child page order number
>thisform.pageframe.pagChild.txtCorrectControl.SetFocus() && specifically name the control
>
>Or loop through the controls on the child page to find the one with the same ControlSource as the grid.column.textbox then set focus that way. The first way is probably quicker, but the second is more generic.
>
>>>Also, PLEASE use parameterized views not a filter to define your child records. >It's harder at the beginning, but MUCH simpler in the long run.
>>
>>So I would be scoping to control inclusion of just those child records which match my background primary key? So as I moved to another parent then I'd set new parameter and use new result cursor? Or would parameter have another scope or function that I'm not understanding?
>
>The easy way to do this is to add the parameter to the child view as the alias.fieldname of the parent view's primary key,
>The code would look something like this:
>
>CREATE SQL VIEW v_Child AS ;
>SELECT * FROM database!child ;
>WHERE child.fkparent = ?v_Parent.pkParent
>
>After you change records on your parent, simply REQUERY("v_child") and refresh the controls.
>The view parameter will look for a variable called v_parent.pkparent.
>
>HTH
Barbara Paltiel, Paltiel Inc.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform