Query Builder

[Jordan]

I have an access 2000/2003 project that is used for data entry into an MS
SQL 2000 back end. All of thd users are using the Access 2003 RT Engine
instead of full Access because I don't want them messing with the data
directly.

I would like to give users the ability to somehow make up their own queries
like I do in the full version with the query builder or like in MSQuery, but
I don't want them to be able to make Update queries.

Is there some sort of add-in or code for a read only form out there that
might help with this?

 

[Douglas J. Steele]

The fact that they're using the runtime doesn't prevent them from being able
to mess with the data directly. What stops them from using some other
client?

To make the query non-updatable, you could always insert the DISTINCT
keyword after SELECT. (Of course, that may give them incorrect results if
they hoped to see multiple occurrances of the same row)

 

[Minton M]

I have an access 2000/2003 project that is used for data entry into an MS
SQL 2000 back end. All of thd users are using the Access 2003 RT Engine
instead of full Access because I don't want them messing with the data
directly.

I would like to give users the ability to somehow make up their own queries
like I do in the full version with the query builder or like in MSQuery, but
I don't want them to be able to make Update queries.

Is there some sort of add-in or code for a read only form out there that
might help with this?

Query design is only available in the full Access version - runtime
doesn't have anything that allows users to create objects.

But if you're using SQL Server 2000, the best solution would be to
create server logins for your users with restricted permissions and
then enable them to create queries using Access (or any other tool).
Relying on users not being savvy enough to change the data is kind of
security through obscurity, which never works.

-- James

 

[Jordan]

Nothing stops anyone from editing any data that they have access to. There
are security groups setup for what data each person can access and edit, but
if a Sales person has access to edit the sales records via the program I
wrote then they can edit them simply via Excel and MSQuery. The only
purpose of the front ends are to control, organize, and present the data in
a usable fashion.

I don't give the users the full version of Access and I use Windows security
features like GPOs and stuff to try prevent any user from installing stuff
to edit the data outside the programs. I would like to encourage them to
data mine for information which is why I was hoping for something to make
read only queries within Access without giving the full version out.