Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Memory Variable problem
Message
De
20/03/2002 01:16:54
 
 
À
19/03/2002 15:19:36
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivie
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Divers
Thread ID:
00634629
Message ID:
00634798
Vues:
21
Hi Hilmar,
Thanks for writing. As far as concern about making indivisual property I could not get how I can solve through form property. Could you give me some detail. how to handle through form property..please...

Situation is I am having almost 50 types of variable for one form which is being used at different text..combo..grid...dtpicker...all type of component is used in form. Somany text using other text memory variable for certain validation. After input all information user pressing save button at that time also some validation required than updating almost 10 table. from memory vaiable.

If I am running form directly its working fine without any error but if i call form through menu/prg its giving some time error at different different text. I tried many time to read all code which calls this form but no any clue.

Solution please.

TIA
>>Hi,
>>
>>I am declaring all variable in .prg and after declaration calling form.
>>At some text when pressing enter its accepting validation but at some text saying not found. If I am putting one linebefore validation at erroneous text like" Varname=Thisform.text1.value
>>Than its working perfectly.
>>Is declaring all variable for particular form in one .prg is ok or should I use some other way. Please guide.
>>
>>Thanks in advance,
>
>If you declare a local variable in a form, they are only visible in the procedure where you declare it - not in the form. Private variables should be visible also in forms you call from the PRG.
>
>To keep things tidy (orderly), you should usually declare all variables in the function or method where they are used. If you need a variable in several methods in a form, use a form property instead (ThisForm.MyProperty).
>
>HTH, Hilmar.
Sajjad Ahmad
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform