Steven

Sorry if this sounds too obvious but wouldn't a single master user file be the best option? In this file would be the all the users, what apps they can access, and what functions inside those apps they can have. In this way its a single user file for which a simple front-end could be written.

>I have developed several applications for my department. In each app I have a table that holds authorized users and level of access(functions within the app they can perform). Many users have access to all the apps and some only one or two. Each app is very different in function example one is a time keeping/scheduling app, another document sign-off app, one is a data submittal app. Anyway, I would like some suggestions on the best way to handle this. Right now if a new employee gets hired I have to add them to each database they will use. I there a way to minimize the data to input?