Link to home
Start Free TrialLog in
Avatar of Andy Brown
Andy BrownFlag for United Kingdom of Great Britain and Northern Ireland

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("UserHasPermissionToEdit")

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
Avatar of Ryan Chong
Ryan Chong
Flag of Singapore image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Andy Brown

ASKER

Thanks guys - I appreciate the quick feedback.