Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Strange but not too important
Message
De
15/04/1998 10:25:16
 
 
À
14/04/1998 19:49:13
Nancy Folsom
Pixel Dust Industries
Washington, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00091768
Message ID:
00092146
Vues:
25
>So, you're kinda making me guess here Sammie <g>, is "Micap" a memory variable and not a field variable? Then, I suspect your problem is because you've bound a control to a variable that has no scope. Try adding "micap" as a custom property of the form, initialize it in the Form Designer, and then you can reference it as thisform.micap (for example).
>
>HTH
>
>>>Do you pick the controlSource from the drop down list of available fields?
>
>...snip
>
>>I just typed in the name. m.micap also gives the same error. The whole thing seems to be related to the word "micap". I remember a 2.5b application I did that the table name the user selected was "cons". Couldn't use the name. Something in win 3.1 must have thought I was calling the Console every time I tried to open the table.

I found the problem. It seems that I had created a logical public var from the command win sometime earlier in the day and the table field is also a logical. The object.value is a numeric so when I tried to use the logical ... you know the rest of the story. Thanks for the help(not much anyone can do for stupidity). Sometimes just trying to explain the problem to someone else causes me, anyway, to really analyse the problem.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform