Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Textbox won't populate it's ControlSource
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Versions des environnements
Visual FoxPro:
VFP 9
OS:
Windows XP SP2
Database:
Visual FoxPro
Divers
Thread ID:
01094039
Message ID:
01094053
Vues:
18
Did the form's dataSession get set to private, thusly causing a scoping issue?

>I've taken over development of a project that was in VFP 8. To begin with I'm moving it to VFP 9 (which should be quite straightforward). This problem may not be related to that, however it could be, I suppose.
>
>Anyway, I've run into a problem on the login form. The ControlSource for the user Id text box was a memvar called _UserCode and the ControlSource for the password textbox was a memvar called _Password. What has started happening is that the ControlSource is not getting populated. So although the textbox value propery is as expected, the control source is empty. I've tried some changes, making the ControlSource a form property, for instance, but still the contents of the textbox are not moved to the control source.
>
>I even created a small replacement form. When run by itself, it works like a champ, but when it's called from the program, it exhibits the same odd behavior described above. So it's like something within the program's environment is causing this, yet I'm at a loss as to what it is.
>
>One specific thing I have noticed: When the replacement form runs standalone, the cursor appears at the right of the User Id textbox because the user ID is numeric. Yet when the replacement form is called from the program, the cursor comes up at the left of the textbox, as if it's a character value. I have stopped program execution and can see that the ControlSource property contains the correct value (thisform.UserId) and that the textbox's value property contains what I typed, but when code is executing in the LostFocus event, thisform.UserId is empty. Again, this is only when the form is called from the program. When running standalone, it works perfectly.
>
>One last thing, I don't believe this started as soon as I pulled it into VFP 8, but I'm not sure. Haven't run into this behavior before. Anyone have any ideas.
>
>Thanks much,
>
>Russell Campbell
Paul A. Busbey
Victoria Insurance
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform