you can now have more than one definition in a relation:
like
recordid <= recordid
value = value
but every line works like a AND-statement.
Is it possible to use a line as an OR-statement?
Do I make sense?
you can now have more than one definition in a relation:
like
recordid <= recordid
value = value
but every line works like a AND-statement.
Is it possible to use a line as an OR-statement?
Do I make sense?
Yes, but not sure how this effects printing for example… seems to me odd things are gona happen.
I wondered how this issue evolved? I think it is an interesting feature to be able to work with or-criteria in relations. The only other way to do this right now is to build your own query.
I didn’t get the remark about printing, btw. Data is data, isn’t it? It doesn’t really matter how it came to be there…
I want to build a valuelist and up to today this is done based on a single relationship recordID=recordID.
I now have to change it but don’t know how to archieve the following:
I am looking for all rows that have the matching fk recordID: recordID=recordID.
But I am also looking for all rows with an empty fk recordID: globals.nullValue=recordID.
However this will be an OR condition. The relationship I build within Servoy only builds AND conditions as far as I can see.
I now have to do this via a query and setValueListItems… Can’t we have this as a standard within Servoy