Hi Larry,

Does that mean that you gave the employees a second FE with only the
ability to generate reports? If so how did you manage to 'remove' the
other functionality in Access?

The Frog

"The Frog" <Mr.Frog.to.you@googlemail.comwrote

Does that mean that you gave the employees a second FE with only the
ability to generate reports? If so how did you manage to 'remove' the
other functionality in Access?

It did use Access' workgroup security (as well as Informix server security),
but the users to whom we provided the capability were not "rogues", and
read-only access to the data prevented inadvertent update problems. In
fact, I don't think we did remove the other functionality. I can remember
helping one of the users create a form to enter "parameters" and run their
report.

This was in Access 2.0 days, and I don't remember the details of
implementing read-only access from this front end -- quite possibly that was
done with the Informix security.

Larry

Larry,
This idea of a 2nd front end is good. I did this sort of thing with
another app 2 years ago that had a SQL Server back end. I basically set
up a 2nd login ID in the SQL Server database that ended in "RO" (for
read-only) and used that login on the startup form of this 2nd front end
.mdb

I'm trying to figure out if there is a way to do this same type of thing
with a 2nd ID where Access is the back end rather than SQL Server.

On this 2nd front end, is there a way in Access to link to the tables
(in my backend .mdb) in a "read-only" state?

RLN


*** Sent via Developersdex http://www.developersdex.com ***

I suspect there is not a way to do so, just considering that you need to
give the user _all_ permissions on the folder where the data is located --
so even outside Access, a user could "do damage" to data in that folder,
whether on purpose or accidentally. But, this is not an area where I really
have any expertise, so someone else would have to provide you a "definitive"
answer.

Larry Linson
Microsoft Office Access MVP


"RLN" <nospamrln@devdex.comwrote in message
news:1212503934_3514@news.newsfeeds.com...

>

>
Larry,
This idea of a 2nd front end is good. I did this sort of thing with
another app 2 years ago that had a SQL Server back end. I basically set
up a 2nd login ID in the SQL Server database that ended in "RO" (for
read-only) and used that login on the startup form of this 2nd front end
mdb
>
I'm trying to figure out if there is a way to do this same type of thing
with a 2nd ID where Access is the back end rather than SQL Server.
>
On this 2nd front end, is there a way in Access to link to the tables
(in my backend .mdb) in a "read-only" state?
>
RLN
>
>
*** Sent via Developersdex http://www.developersdex.com ***