Currently in Servoy you have a choice (at the form property level) to use the same foundset being used by other forms (using the same table) or a “separate” foundset. It would really be nice to be able to give a foundset a name and be able to request that certain forms use a certain foundset with that name.
So there would be three options for a form’s foundset:
1). Default (the foundset shared by all forms using the same table)
2). Separate (a seperate foundset for a given table)
3). A foundset of name “foo”
**I am referring to a form property not a foundset object gotten programatically.
Maybe my thinking is wrong but once you ‘name’ a foundset on a form you would also ‘pick up’ that foundset from that form (am I clear).
If so what would be the benefit over named foundsets because you would refer to that foundset anyway?
Or, in other words, what would be the benefit of named foundset over setting them in a method and how do you see that happening?
You mean you want multiple shared foundsets. Right now you only have 1 shared foundset where Servoy takes care of all ‘communication’ between the forms that use this shared foundset (change selection, etc).
The moment you use a seperate foundset you need to code this ‘communication’ between other forms with seperate foundsets yourself.
Now with ‘named’ foundsets you could pre-define such a foundset on a table and let different forms use this.
I (and a bunch of other developers) have wanted this since a long time (1.2?) so YES you have my vote on this one
ROCLASI:
You mean you want multiple shared foundsets.
That would be a great feature, to have multiple shared foundsets.
That possibility would be very welcome in my solutions.
Now I’m copying all the time foundsets to a form, because it is the only way to maintain the correct foundset to the correct form