Lawson-supplied MSS Role

I completely scrapped the idea of using Lawson's classes for MSS, and built my own. One functions as planned, but is very very slow (up to 2 minutes to return accessible employees). The other is very fast, but the view on the returned data is different (employees are sorted on Employee Groups, and no filtering seems to have been applied). Below are the two rules written against the EMPLOYEE table in question:

- user.isInChainOfCmdOfEmpInHR(lztrim(table.COMPANY),lztrim(table.EMPLOYEE)) - very slow, dead on accurate data.

- user.isSupervisorOfEmpInHR(lztrim(table.COMPANY),lztrim(table.EMPLOYEE)) - very fast, but essentially useless.

We are not using element groups, not using ESS, using LSF 9.0 and LS on Windows. Would anyone be able to tell me how to speed the searches up? I really hate that I may have to resort to using process levels to control access, especially after spending a couple of months making sure our supervisor table is dead accurate.

Frank, I am not sure if this applies here but I know in the past when I run into issues with performance of employee queries we would explicitly define the company, adding a where company = xxxx to the statement and this would greatly improve response time. If you do not have more than one HR company this may help.

Thank you for the help! Your technique did cut the wait down to about 1 minute. Just so I am clear on what suggested, here is what I used:
user.isInChainOfCmdOfEmpInHR(trim('100'),lztrim(table.EMPLOYEE))

Since we are not using RSS, I tried entering a supervisor code into the REQUESTER ID field. The response on this was almost instant, but of course this removes alot of the functionality of linking positions to HRSUPER entries. We are really digging for viable options here!