addTableFilterParam no longer works

Hello. I have a solution that works great on one server, but I’m migrating it to a new server and having trouble. Both servers are running Servoy 5.0.1 and the Sybase database that came installed by default.
On the new server I used SQL Anywhere 12 to create a service to run the database, configured sybase.config, etc. Servoy app server service is also running.

When the solution launches, it is supposed to apply the following filter:

databaseManager.addTableFilterParam('example_data', 'facility_info', 'cage', '=', groupName, 'facFilter')

Using my new server\database, this no longer works. When I launch the solution from an external smart client, I can see my data, but the filter does not get applied correctly. However, when I stop the services from running and launch Servoy Developer on the server, and then connect to the solution from an external smart client, the filter IS applied correctly.

So it seems that when developer is running, the app server and database connections that it uses interprets my code corerctly, but when I run it as a service, it doesn’t work. Again, the same setup on my old server works, the only difference is that on that server I used SQL Anywhere 11 to create the service, and on the new server I used SQL Anywhere 12.

thanks for any thoughts!

Do you have any errors in the log?

Please consider upgrading to 5.2.9, there have been a lot of fixes since 5.0.1.

there’s nothing in the server log, where else would I look? thanks.

Does the addTableFilterParam() call return true in the smart client?

Maybe the server name is different from the developer or from the appserver (are the server definitions in the servoy.properties files the same)?

Rob