Read only security for certain tables without using workgroups

[storl2]

I searched around, but did not see a thread or FAQ on this.

I have a database where the front end and back end are separated. The front end is about as secure as it can be, and I want to keep it that way. I need to have a few select people be able to create ad hoc queries off of the backend, since several departments are using this database for executive reporting.

Is there a way to create another database that links in to the backend's tables, and has read-only access to those tables without using workgroups? The people will need to be able to create and edit their own queries and reports, just not be able to edit the tables.

Thanks!

 

[stix4t2]

Have you tried creating a hidden form that uses the tables. If the table is in use it cannot be modified. You can set the form at startup but keep it hidden.

 

[storl2]

It's not that I don't want them to be able to edit the design, it's that I don't want them to be able to edit anything, including the data in the tables. I want them to just be able to query off of it.

 

[StarPassing]

In the FE use code to open the BE database with the Read-Only option set to True. Then link the tables they need in the BE - these will be read-only. See 'OpenDatabase' in the help system.

 

[BoxHead]

storl2

Take a look at Dev Ashish's form for dynamically building and exporting queries.

It may be helpful

thread702-1193691


HTH


John



When Galileo theorized that Aristotle's view of the Universe contained errors, he was labeled a fool.
It wasn't until he proved it that he was called dangerous.

 

[storl2]

StarPassing:

I am not sure I understand what they are doing in that OpenDatabase example. Once you open the database and link the tables, do those links stay there, or does it relink each time they open the querying database?

I can't seem to wrap my head around the "workspace" concept they talk about.