I want to build an application where part of the information (the confidential part) stays on a local database at the clientside, and is thus different for every client. Is this possible with servoy, or eventually with the future “offline client”?
Why do this in another database?
You can use “addFoundsetFilter” on load of the form.
HTH
Stef
I want to let confidential information clientside (for example patient-names etc), thus not saved on the master-database. Because the clients reside on different geografic locations, there seems no other solutions to me, than let them have a database on every location.
I don’t know that you will ever be able to do this in Servoy.
Here’s why: The solution you create needs to have a named connection to one or more databases so we can connect and do all the SQL stuff necessary. If you have a DIFFERENT setup for each CLIENT, then it will be impossible to have local data pointed to by the named connection for each different client.
I’m not on the engineering staff at Servoy, but that’s my take on the situation - I COULD BE WRONG.
Cheers,
Bob Cusick
Hi, ive set up an foundsetfilterparam in a tab panel within a module.
when i work use the foundsetfilterparam in the module from developer it works no problem. When i open another solutions that uses the same module the foundsetfilterparam does not work
anyone had this? is it a bug or something im doing?
is there a simple way to filter data just one form at a time so that filter no longer applies when you leave that form?
im using the form addfoundsetfilterparam in the module through a reliationship but i cant see why that should stop the filter working
is it more efficient to filter by adding another column to the relationship rather than trying to use addfoundsetfilterparam… id have to add a bogus column to one of the tables if that was the case
ive been through the “filtering found set” tuition by Bob Cuisack http://www.servoymagazine.com/home/2004 … ering.html
this was very helpful but as it explains in there, any foundsetfilterparam stays applied for the whole session rather than just for one form. i guess there must be a simple way of doing this.. any ideas much appreciated
many thanks
megaquests:
I guess there must be a simple way of doing this.. any ideas much appreciatedmany thanks
Why don’t you use the username as a filter in the relation?
You add a column ‘owner’ to the child table and setup a global field with the current user username in the parent table, then the relation is as follow:
parent child
a =a
b =b
... ....
globals.user=owner
This way you can store all data in the same table and present users only their personal data without the need of a FilterParam.
Obviuosly data should be accessed only via the relation and not via other forms or direct queries.
Just my 2 cents.
thanks Nicola
for this particular filter it is not user related…
it simply a case of wanting to show paid and unpaid customers in a table rather than showing them mixed together..
perhaps ive posted this in the wrong thread.. it was closest i could find to this problem