Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Error 1736 on new editbox
Message
De
22/03/2016 08:09:51
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Allemagne
 
 
À
22/03/2016 07:21:14
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows 10
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01633174
Message ID:
01633489
Vues:
59
>>Hi Tamar,
>>
>>do you have code to reproduce that? I still do noz understand why this ends uo in Error 1736
>>
>
>I think the key piece is that the second form was a form class being instantiated by CreateObject() rather than run with DO FORM.
>
>Tamar

I've seen Naomi post.

I've spend a while why I could not reproduce (I've tried with my normal stuff.)

After I've gone back to a plain form I was able to reproduce it.

What I have done other then a standard form is: my standard for forms is BINDCONTROLS = .F. For that the object does not look for the controlsource while instantiating. If I set BINDCONTROLS = .T. later on you get something (more) meaningfull like VARIABLE (fieldname) not found in the moment it kicks in. Still not pretty well, but since a Controlsource could be a variable I can live with.

IOW the error means: The object fails due to a wrong controlsource, returns .f. on init and the form complains. Not a nice way.
I think BINDCONTROLS = .F. must have saved my day many times. :D
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord

Weeks of programming can save you hours of planning.

Off

There is no place like [::1]
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform