Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
ActivePage...Not!
Message
De
08/05/2001 08:06:35
Jay Johengen
Altamahaw-Ossipee, Caroline du Nord, États-Unis
 
 
À
07/05/2001 00:28:21
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Divers
Thread ID:
00503661
Message ID:
00504628
Vues:
22
Dragan,

Thanks for the information on this. Couple things I want to understand on what you said...

>The only way I got it to work was
>oPageRef.parent.activepage=oPageRef.pageorder

Assume I issue your code above from a method and oPageRef is referencing Page3 on a pageframe. Does that mean that the active page is set to the pageframe's PageOrder of Page3 (which may be unknown to us) and Page3 will be activated? Where would you put this code?

>I'd rather not use evaluate() either, if possible. Instead of passing the page's name (which we can't be too sure of, i.e. can anyone be sure the 4th page >will be named page4, and that the "page"+trans(i) will give the right name for each page?), I prefer passing the page's number, and then
>loPage=thisform.t48_page_frame1.pages[m.nLastPage]

Why are macro substitution and evaluate unreliable? I've heard that before, but never understood why?

To digress slightly from your reply and address something I posed earlier in the thread, when should you use the Valid as opposed to the Click methods?

Thanks! Renoir
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform