I have just been trying to see if its possible to secure the backend of my access database. I have searched the forums but couldn't quite see the answer.
The current setup is that the frontend is distributed as a runtime accde and run on the clients locally and the backend sits on a windows file server.
As far as I can see there is no way to set the ntfs/share permissions on the domain to restrict browsing to the unc path where the backend is located and either copying or deleting the backend. Is this correct?
My only thoughts are too obscure the files by using hidden shares and restricting access to the windows network explorer. Are there any other better ways to do this?
The current setup is that the frontend is distributed as a runtime accde and run on the clients locally and the backend sits on a windows file server.
As far as I can see there is no way to set the ntfs/share permissions on the domain to restrict browsing to the unc path where the backend is located and either copying or deleting the backend. Is this correct?
My only thoughts are too obscure the files by using hidden shares and restricting access to the windows network explorer. Are there any other better ways to do this?