Equivalent VB6 "Limit to List"

[Ian Bayly]

Hi
I suspect I know the answer (No), but it's worth an ask!

When coding with a combo or listbox, is there a technique whereby a new value can be entered into the control, and code added, to add the item to the control source?

The only alternative I see is to have an "add" button and use this to add new items.

Ian B   

[TechSupport]

Hi Ian,

I have no idea what you're talking about....

Do you mean adding strings to the combobox/listbox at design time? If yes, then FireFly 3 has this functionality. FireFly 2 does not. In FireFly 2 you need to add the data in the WM_CREATE message handler. That's what I use (well, I don't use FF2 anymore... )

[Ian Bayly]

Sorry All

"Limit to list" and the event "not in list" are not present in VB6 but only in VBA for MS Access.  I should have checked VB before posting.
FWIW it allows a combo box to be used to add a new row to the underlying records by typing a new entry into the combo box.

Apologies again

Ian B 

[TechSupport]

Oh, so you mean something like a data bound control. I had used such a feature many years ago with Visual Basic. A couple of people sugessted data bound controls to work with Cheetah and/or SQLite. I can honestly say that you will never see such a feature in FireFly (sorry). I remember reading from the Visual Basic Gurus many years ago that data bound controls are more trouble than they are worth.

I noticed over on Jose's forum you posted about ADO/DAO. So you're using DAO for your data access, right? I guess it is because you need to interface to an MS Access database? There are dependencies with DAO - well at least there used to be. I remember having to deploy the DAO package with my InstallShield installations whenever I sent out my Visual Basic program.

If you don't need MS Access databases then maybe you could take a look at our SQLitening product. It's free, small and wicked fast. 

[Ian Bayly]

Thanks for the comments Paul.

Not exactly like a databound control, but I can work around in FireFly with another approach.
Looked at SQLitening but I suppose I was clinging to "a security blanket" sticking with Access.

Looks like a wet weekend coming up so I will have a serious look at SQLitening.

Ian B