Multiple search criteria not working for more than 2

I have a Servoy solution which has recently been upgraded from Servoy 3.5 to 5.2, and from Sybase 9 to Sybase 11. It is running on a Mac server with the latest Java and etc. Previously Servoy would allow multiple search criteria (new request) to build up a search. Now, it works for 2 requests, but any further requests are ignored. Is this a bug or do I need to do something in my code to re-enable it (it does seem odd that it allows two search requests but not more). Nothing else has changed in the solution and it was definitely working previously.

Any help would be appreciated.

Thanks

Bevil

Bevil,

The number of records in find mode is not limited, this is unchanged since Servoy 3.5.
Can you show some sample code?

Rob

Just before, you fire this search, clear the performance tab in your servoy-admin page.
than fire the method with this search, and look again in the performance tab and see what query Servoy makes of this…

Thanks Rob and Harjo

Unfortunately I was quoting the client directly and didn’t actually test it until now (I posted the question when I didn’t have access to the solution, slack, I know…).

It turns out that the reason that this is happening is that the field that they’re trying to search is nr. 1 in the tab sequence. Therefore, you hit CMD-F to enter find mode, type a number into the auto selected field, then hit CMD-N to make a new request, and it again gives you a blank find mode form, and selects the correct field, and you type another number, but if you hit CMD-N again, this is when it doesn’t work.

To work around the problem, I can tab out of the field before every CMD-N, but it is inconsistent behaviour (works for 2 but not more). There is not really any code to send or check… I think it is just to do with the field being first in the list - and it was changed to this behaviour during our upgrade…

Is there any way to have the correct field selected on find command, but allow it to repeat the process multiple times?

Thanks

Bevil

can you make a small example and attach that to a case?
reading your description that should work just fine.

Hi Johan,

I have made a case, number 343127.

Bevil,

The problem only happens when during find and new-record the user never leaves the same search field.

This is now fixed in 5.2.5.

Rob