Re: Deploying my App

You can secure the back-end, or just hide anyway for the user to get at it.
When deploying an app with a Terminal Server, you should always make a copy
for each user and put it in a folder that has all of their applications, and
is unique to each user. Sharing a front-end can lead to corruption.

I always place the back end on another server, but there is no real
advantage other than ease of backup, or if your back-end is SQl-Server, you
can better allocate resources.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

"RobUCSD" <RobUCSD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B8122F59-E6E7-401B-88F2-83779486CB42@xxxxxxxxxxxxxxxx
My application will be deployed via citrix on Monday. My question is how
can
I access the user level security wizard if I split the database, create a
MDE
front end and disable MS Access special keys and open the front end
without
the access toolbars?

Is there another way to add users, groups, set passwords other than the
security wizard?

Can I use the same mdw file to secure the back end?

Thanks for your help. rob


.

Relevant Pages

  • Re: How to Publishing applications on Terminal Server 2003?
    ... Microsoft MVP - Terminal Server ... >The IIS server is already used for secure OWA. ... >applications through RDP. ... >Patrick Rouse ...
    (microsoft.public.windows.terminal_services)
  • Re: Saving files back to local computer
    ... SSL is reasonably secure. ... I'm of the opinion that any open ports are ... > unless you map a public IP to each private Terminal Server. ... has an SSL Gateway Built-into their products, ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Server through the Internet
    ... In no way is that secure. ... Microsoft MVP - Terminal Server ... We are just deploying a new terminal server in our organisation, ... Most of our users use a Remote Client software to create a VPN tunnel, ...
    (microsoft.public.windows.terminal_services)
  • Re: Publish Terminal Server on Internet
    ... That solution is precisely as secure as your Terminal Server. ... If you have secure passwords and good security and patching practices, then Windows can be made to be very secure. ... This is not a security threat in the normal sense, and will not result in your machine being comprimised, but for a comparatively small ammount of attack resources, a comparatively large amount of server resourses are consumed. ... Change the port number for the RDP listener on your internal TS Server to ...
    (microsoft.public.windows.terminal_services)
  • Secure BE
    ... I'm having traouble figuring out how to secure the ... I load the FE which is secured onto all the clients and ... FE's tables are all linked to the BE which is stored on the server. ... I'm trying to avoid clients getting into the back-end at all. ...
    (microsoft.public.access.security)