Re: Security on a common server
- From: "hackmn_g" <hackmng@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 26 Apr 2005 10:34:03 -0700
How would I go about creating an installer? Would I then have to change the
file path that is currently pointing to the user's Access installation in the
shortcut target?
"Paul Overway" wrote:
> Assuming all users have the share with the MDW available to them, including
> appropriate file permissions...AND msaccess.exe is installed in the same
> location on all users/PCs...AND the database is also installed in the same
> location for all users/PCs....you can create the shortcut as suggested
> earlier and put it on the share and/or email it to your users. If any of
> the the files might be installed in different locations for different
> users....you need to create an installer that will analyze the user's
> environment and create the shortcut accordingly.
>
> --
> Paul Overway
> Logico Solutions
> http://www.logico-solutions.com
>
>
> "hackmn_g" <hackmng@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:CE95456B-1525-4656-8EB2-033740F19360@xxxxxxxxxxxxxxxx
> > All: Okay, I've created a NEW workgroup information file. It is sitting
> > on
> > the server and is called Secured.mdw. When I go to open the database (mdb
> > file), it says I don't have necessary permissions. However, when I go
> > into
> > Access and "Join" to this Secured.mdw workgroup information file, I can
> > access the database. I think all of you mentioned setting up a shortcut
> > for
> > the users that will set their workgroup information file to look at
> > Secured.mdw and get them into the mdb file. How is this accomplished?
> > Thanks again!
> >
> > "hackmn_g" wrote:
> >
> >> The History: Being an inexperienced Access developer (and not even an IT
> >> person!), but being rushed into building a database for my company,
> >> security
> >> has become the thorn in my side. I created security, bypassing the
> >> wizard.
> >> I copied the database onto a common server where users would use the
> >> database. When I tested the database on another computer, no logon
> >> prompt
> >> came up. After reading through some of the posts here and reading
> >> through
> >> the Access Security FAQs page, I unsecured the database and imported
> >> everything into a new database, still sitting on the common server. I
> >> was
> >> able to run the wizard and set security up through it.
> >>
> >> The Questions: Being that this database is sitting on a common server for
> >> the users to access, how can I secure the database? I am sure that the
> >> lack
> >> of a logon prompt from another computer has to do with the workgroup
> >> information file sitting on my local machine. Can I simply copy the
> >> system.mdw file onto the server? If so, will I then need to join each
> >> individual's machine to refer to this workgroup information file sitting
> >> on
> >> the common server? Is there an easy way of doing this? Can a user's
> >> machine
> >> refer to more than one workgroup information file, in case he/she has a
> >> local
> >> database?
> >>
> >> Thanks in advance.
>
>
>
.
- Follow-Ups:
- Re: Security on a common server
- From: Paul Overway
- Re: Security on a common server
- References:
- Security on a common server
- From: hackmn_g
- RE: Security on a common server
- From: hackmn_g
- Re: Security on a common server
- From: Paul Overway
- Security on a common server
- Prev by Date: Re: Security on a common server
- Next by Date: Re: Security on a common server
- Previous by thread: Re: Security on a common server
- Next by thread: Re: Security on a common server
- Index(es):
Relevant Pages
|
