R
robert d via AccessMonster.com
I want to propose to a client that we use my Access app via terminal services
from a website that they also want us to develop. I'm proposing another
company to do the website development as I know next to nothing about it.
However, they don't know much about Access. In this discussion "app" refers
to the front end as we will be using a SQL Server backend.
Problem: Client wants single user sign on.
My Access app has workgroup security applied to it. Probably even more
important, depending on the group the user belongs to, the menu bars are set
accordingly (i.e. Admins have more menu 'tools' available to them than do
Users).
Currently my app uses a separate small Access .mde file for logging on. The
logon .mde puts together the shortcut for opening the main app. It also
allows for downloading a new copy of the app to the local PC if one is found
on a central server. However, this functionality will not be needed if the
app is launched from a website link that opens terminal services.
Questions:
1) So assuming we create a logon web page, then I would guess we could open
the logon .mde for my app and transfer the user name and password from the
web page to the logon form, maybe using some kind of scripting (I don't know
anything about this either). Then could we remotely click on the button on
the logon .mde to have the app launched. Alternative ideas and approaches
are welcome.
2) I see the bigger problem as how does one setup new users for both the
website (which has other functionality) and my app. I see no way around
having to do this twice. Once for the website and once for my application.
Any recommendations on this are greatly appreciated.
Thanks.
from a website that they also want us to develop. I'm proposing another
company to do the website development as I know next to nothing about it.
However, they don't know much about Access. In this discussion "app" refers
to the front end as we will be using a SQL Server backend.
Problem: Client wants single user sign on.
My Access app has workgroup security applied to it. Probably even more
important, depending on the group the user belongs to, the menu bars are set
accordingly (i.e. Admins have more menu 'tools' available to them than do
Users).
Currently my app uses a separate small Access .mde file for logging on. The
logon .mde puts together the shortcut for opening the main app. It also
allows for downloading a new copy of the app to the local PC if one is found
on a central server. However, this functionality will not be needed if the
app is launched from a website link that opens terminal services.
Questions:
1) So assuming we create a logon web page, then I would guess we could open
the logon .mde for my app and transfer the user name and password from the
web page to the logon form, maybe using some kind of scripting (I don't know
anything about this either). Then could we remotely click on the button on
the logon .mde to have the app launched. Alternative ideas and approaches
are welcome.
2) I see the bigger problem as how does one setup new users for both the
website (which has other functionality) and my app. I see no way around
having to do this twice. Once for the website and once for my application.
Any recommendations on this are greatly appreciated.
Thanks.