I must admit I developed the technique for working with faceless classes
In this app the interface has to talk to three databases
So I put them I a DBDictionary (part of a Module)
DBDictionary.Value("localportfolio") = new ValDB --> subclass of
Valentina Database
I have subclassed all relevant interface-controls
(listboxes,editfield,radiobuttons,checkboxes,...)
These subclasses have a property (visible in property pane) DBToTalkTo
Whenever I need the control to talk to a database, I tell it to
Dim myDB as ValDB
myDB = DBDictionary.Value(DBToTalkTo)---> has been set in the IDE but
of course can change during runtime
and this control switches the database it needs to talk to
Works very smooth once you have it running
Bart
On 7-mei-07, at 20:33, Norman Palardy wrote:
>
> On 7-May-07, at 10:38 AM, Bart Pietercil wrote:
>
>> But why would I need control arrays if i have controls addressable by
>> name :-)
>> if I know that radiobutton1 and radiobutton2 need to be checked
>> against each other I just retrieve those two from the ControlDict
>
> Cloning a control needs it to be a member of a control array
> _______________________________________________
> Unsubscribe or switch delivery mode:
> <http://www.realsoftware.com/support/listmanager/>
>
> Search the archives:
> <http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
