alevin16
asked on
An issue with putting the backend of an Access database in a folder on a server and accdc issue
Hello All
Here is my situation. I have created an Access database and will be putting the backend on a server that everyone will have access to. Is there a way to allow each user to access the tables ONLY thru my front end of the program? What I do not want a user to be able to do is open up the back end in a folder window and access the tables directly.
In a related issue, when I split the database it creates an accdc file. I need to be able to add more tables to the back end and I am not sure how to work with an accdc file.
Thanks to everyone again!
Here is my situation. I have created an Access database and will be putting the backend on a server that everyone will have access to. Is there a way to allow each user to access the tables ONLY thru my front end of the program? What I do not want a user to be able to do is open up the back end in a folder window and access the tables directly.
In a related issue, when I split the database it creates an accdc file. I need to be able to add more tables to the back end and I am not sure how to work with an accdc file.
Thanks to everyone again!
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.
You are welcome!
/gustav
/gustav
You can get what you want by protecting the FE (distributing as a accde) and using folder security.
What you do is place the BE in a subfolder of a data directory. On the main data directory, you give users Traverse Folder rights only. Might look like this:
X:\AppData
\xyz32
\MyAppdata.Accdb
When they look in X:\appdata, they will see nothing but an empty directory, but can they can "jump over" \xyz32 to get to the data. However they need to know the sub directory name.
So as long as you never expose the full path to the user in the app, then they can't get at the backend except through the app (which knows the path).
But I agree with the others; SQL Server would be a far better choice if your concerned about security.
Jim.
What you do is place the BE in a subfolder of a data directory. On the main data directory, you give users Traverse Folder rights only. Might look like this:
X:\AppData
\xyz32
\MyAppdata.Accdb
When they look in X:\appdata, they will see nothing but an empty directory, but can they can "jump over" \xyz32 to get to the data. However they need to know the sub directory name.
So as long as you never expose the full path to the user in the app, then they can't get at the backend except through the app (which knows the path).
But I agree with the others; SQL Server would be a far better choice if your concerned about security.
Jim.
ASKER