Andy Brown
asked on
Should I keep recordsets open?
My Access database uses three tables (running off of the local PC - not network), to help with user permissions, project settings, and application settings. Currently, I have a function that pulls in the necessary values when required. For example, "can a user edit a record?" would be:
TSUserPermissions("UserHas Permission ToEdit")
The function itself uses the Elookup function created by Alleen Browne to search and return the value - and it seems to work well.
However, there could be several of these calls within a minute on the three tables, and I was wondering if I would be better off creating a recordset for each of them and leaving them open (unless you can see a better way)?
Thanks as always.
TSUserPermissions("UserHas
The function itself uses the Elookup function created by Alleen Browne to search and return the value - and it seems to work well.
However, there could be several of these calls within a minute on the three tables, and I was wondering if I would be better off creating a recordset for each of them and leaving them open (unless you can see a better way)?
Thanks as always.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER