Hiding Queries

[Derek]

I have a SQL Server database which a user wants to query. This user is competent with Access, so I have created an Access database with read only linked tables for them. They now have around 50 queries

I now have a second user who wants to do the same thing. There will probably be more users in the future. Because of this I don't want to create an access database for each user. However it is not practical to have them all on one database as they will start to lose their queries amongst everyone else's

What I would like to do is have a login where only the individual's queries are visible to that user. However the User security stuff doesn't seem to make things invisible, just stops you from using them

Obviously the users I am talking about know what they are doing. Furthermore there are no security requirements, and I'm pretty happy to give them complete access to everything. I just want to keep things tidy

Any ideas appreciated

 

[Rick Brandt]

I have a SQL Server database which a user wants to query. This user is

competent with Access, so I have created an Access database with read only
linked tables for them. They now have around 50 queries.

I now have a second user who wants to do the same thing. There will

probably be more users in the future. Because of this I don't want to
create an access database for each user. However it is not practical to
have them all on one database as they will start to lose their queries
amongst everyone else's.

Why not give them each their own file? You keep a template with just the
Read-Only links in it and you make a copy for any time someone asks for it.
Multiple users should never share the same file anyway.

 

[Derek]

Delivery of this is probably going to be across Citrix. I want to retain control of who can get to the access program. I can control this in Citrix. (ie Users can't pass the access file on to another user and say, oh, just use my login.

Inside Citrix I was hoping to avoid having quite a few applications (one for each person). If I have to then I will, but I would prefer not to

Any other ideas

Thank
Dere

----- Rick Brandt wrote: ----

I have a SQL Server database which a user wants to query. This user i

competent with Access, so I have created an Access database with read onl
linked tables for them. They now have around 50 queriesprobably be more users in the future. Because of this I don't want t
create an access database for each user. However it is not practical t
have them all on one database as they will start to lose their querie
amongst everyone else's

Why not give them each their own file? You keep a template with just th
Read-Only links in it and you make a copy for any time someone asks for it
Multiple users should never share the same file anyway