Looking for 3rd party Query Builder that doesnt allow edits

[Micron]

I'm no Active Directory expert but don't see that suggestion working. Permissions are assigned to the folder, not the files. Access has to create the lock file (e.g. ldb) as I said, so one must have create and delete rights to the folder in order to place and remove that file. That exposes the back end to the point where protecting the db becomes impossible.



Maybe you are referring to the old Access security model and not folder permissions?

[Homegrownandy]

would it not be easier to anticipate the kind of querys they would need and have drop boxes where the user could pick parameters.

[John_G]

Most networks these days do have file-level permissions. Your network administrators can set the permissions on the database files do that only those users who are authorized can update the data (write permission); everyone else is read-only. Since you are using a split database, the front-ends are on everyone's own machine, where permissions on the front-end databases are not an issue. Users can create whatever select queries they require without a problem, and if they had the required knowledge, they could create reports as well. They could create update queries too, of course, but if the backend is read-only, the queries wouldn't do anything.

So, as long as your network has file-level permissions, it should be easy to implement your requirement.