Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
ComboBox
Message
De
16/01/2017 00:34:45
 
 
À
15/01/2017 16:45:49
Information générale
Forum:
Visual FoxPro
Catégorie:
Classes - VCX
Titre:
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows 10
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01646654
Message ID:
01646693
Vues:
65
>>>My "base" combo has calls in both Init and Requery to a custom GetItems method. Code to populate goes into GetItems. I've never had any problem with this.
>>>
>>>And if trying to implement it like this doesn't work, maybe Tamar can send you her machine {just to be clear, this is a joke}. I just love it when the response to a request for help is "Well it works on my machine". To which my response is "Then please send me your machine" :)
>>
>>In this case, I was making a specific recommendation to NOT call Requery from Init, but rather to have both of them call a common method. I wasn't just saying "it works on my machine."
>>
>>Tamar
>Tamar,
>that helped. Still for me understandable how it happens that pemstatus(myCombo,'Listcount',5) shows true and still it errors. Noway to check / prevent this error?
>Regards,
>Koen

I've had occasional problems whenever I tried using SQL as a rowsource for listbox and combobox. Works without a hitch if the listbox rowsource is essentially constant, but got into weirdness when underlying query was re-generated by performing reuery() on the control. Sometimes it would work, and sometimes it would behave as if the underlying query had failed to generate a cursor. Ended kludging a workaround by setting rowsource type to alias, then performing the query in a method (this method would first clear the rowsource value, then perform the query to create the cursor, then assign the rowsource to the cursor name).
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform