If your Act! database does not use the limited access security feature in Act!, then it would be nice to remove the limited access checking from the stored procedures in the backend SQL database. The larger your database gets, the slower it will be. Removing the limited access checking speeds things up quite a bit based on our testing.
If a company decides they need to use limited access, check a box in tools>>preferences>>admin which would then write the code to turn the feature on.
"Removing the limited access checking speeds things up quite a bit based on our testing."
Interesting. How do you remove Limited Access checking, exactly?
It's not something you can do using the UI (User Interface). You have to modify things on the backend.
Everytime Act! builds a list view, or does a lookup, or pulls up a report, etc... it does a security check on what you're doing to make sure you only see what you should be seeing, as it should. The problem is, if you aren't using security it starts to slow things down quite a bit. This is only an issue for probably 5% of Act! users out there. But, for those of us that have it, it's a nightmare.
@Hammatime wrote:If your Act! database does not use the limited access security feature in Act!, then it would be nice to remove the limited access checking from the stored procedures in the backend SQL database. The larger your database gets, the slower it will be. Removing the limited access checking speeds things up quite a bit based on our testing.
If a company decides they need to use limited access, check a box in tools>>preferences>>admin which would then write the code to turn the feature on.
Can you share this trick in the 'Backend' please.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.