Data access pages on intranet

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am trying to set up read-only data access pages on an intranet, which would
allow those employees in our firm (30-40) who do not have Access on their
machines to look up basic data (like phone numbers and addresses).

Right now, the system uses user-group based security, with front ends on the
machines of each person who has Access (either 2003 or 97), which are linked
to a back end in Access97 which lives on the server.

The data access pages that I have managed to get running (marginally--I'm
finding this aspect of Access much less easy than the books imply) require
the user to log-in every time they open a new page. Especially if I am using
forms to navigate between forms (a feature I am still struggling to make
work) , this is too much.

I already have the pages locked so that the user cannot add or delete data.

How do I make these pages so that we do not need the user to join the group
again with every page to which they navigate?

Thanks for your help.
 
If there is an answer here to my access problem, with the security system and
the way that it interfaces with data access pages, could you point me in a
specific direction on that site? What you appear to have provided is an
advertisement for an alternate system to replace Access in this mode.
 
After a substantial time of frustration, I have finally stumbled on the
answer, which I list here in case someone else is frantically trying to do
the same thing.

In the design view of the data access page, go to page properties.
Under Data, there is a Connection String. Click on "Build" for this
property and it will bring up, among other things, a security selection
place. One can elect not to have a blank password, and to "remember" the
password. This allows me to set the password at the very simple userID and
password that I maintain for read-only users. For my purposes, it does not
matter that this makes that password public for anyone who wants to go
looking in the code. Within the company, it never was a secret. And this
does allow my users to move from webpage to webpage without being prompted
for userID and password at each page.
 
Back
Top