Re: Basic security questions

So you have to provide the mdw in the connection string for this to work.
Why don't you have to give the full path to the mdw, but you do with the
database?

Thanks;

Amy

"Scott McDaniel" <scott@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:WPOdnWXCa4QeYpneRVn-jg@xxxxxxxxxxxxxx
> Your ASP page would "connect" to the file on the Unix box via ADO or
> ADO.NET ... I'm not familiar with .NET, but with ADO your connect string
> would look something like this:
>
> oConn.Open "Provider=Microsoft.Jet.OLEDB.4.0;" & _
> "Data Source=c:\somepath\mydb.mdb;" & _
> "Jet OLEDB:System Database=MySystem.mdw", _
> "myUsername", "myPassword"
>
> Connect string from here:
> http://www.carlprothman.net/Default.aspx?tabid=87#OLEDBProviderForMicrosoftJet
>
> Your connection would actually use the .mdw file (probably on the Unix box
> as well) to "open" the database ... your ASP server would handle the rest.
>
> Password protected databases are different from database protected by ULS
> ... password protection travels with the database and requires no external
> files. ULS protected databases require the use of the .mdw workgroup file
> (which stores Users, Groups, GroupMemberships, and Passwords) and the
> database itself ... the .mdw file simply authenticates the user and tells
> the db which groups the current user belongs to ... the acutal object
> permissions are stored in the database itself.
>
> --
> Scott McDaniel
> InfoTrakker Software
> "Amy Blankenship" <Amy_nospam@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:uowPmvCpFHA.568@xxxxxxxxxxxxxxxxxxxxxxx
>> So if I put the file on A UNIX server, for instance, and I wanted to pass
>> a user name and password from an ASP page and windows isn't actually
>> involved, what would the process look like then?
>>
>> And I've also gotten password-protected databases from people in the past
>> where I didn't change any files on my computer, but somehow when I
>> double-clicked on the file it asked for a password and let me in when I
>> provided it. What was the mechanism for this series of events?
>>
>> Thanks;
>>
>> Amy
>>
>> "TC" <aatcbbtccctc@xxxxxxxxx> wrote in message
>> news:1124355840.119252.135890@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>
>>> Amy Blankenship wrote:
>>>
>>> (snip)
>>>
>>>> Barring that, I'd like to have the database look for its workgroup file
>>>> in
>>>> the same directory as itself.
>>>
>>> You misunderstand how it works. Access selects a workgroup file before
>>> it even /opens/ your database. The database itself plays /no part
>>> whatever/ in Access'es decision on which workgroup file to use.
>>>
>>> If you double-click an mdb file, the sequence of actions is as follows.
>>>
>>> 1. Windows determines that mdb files, should be opened with MS Access;
>>> 2. Windows starts MS Access, passing the mdb file name as a parameter;
>>> 3. MS Access opens the default workgroup file for that PC;
>>> 4. MS Access /then/ opens the specified mdb file, then
>>> 5, The mdb file works, or doesn't work, depending on whether it is or
>>> is not usable with the PC's default workgroup file.
>>>
>>> When you secure an mdb correctly, you create a new workgroup file, and
>>> the mdb file will /not/ work with the default workgroup file. So if you
>>> double-click that mdb file, it will fail, because Access will use the
>>> defauilt workgroup file, exactly as described above.
>>>
>>> When you start an mdb file using a shortcut of the standard form, shown
>>> below, Access starts, then opens the /specified/ workgroup file
>>> (regardless of the PC's default workgroup file), then opens the mdb
>>> file. You must use the shortcut approach when opening a
>>> properly-secured mdb file.
>>>
>>> "full path to MSACCESS.EXE"
>>> "full path to MDB file"
>>> /wrkgrp "full path to MDW file"
>>>
>>> In summary, there is no situation where "the database looks for the
>>> workgroup file". It simply does not work like that.
>>>
>>> HTH,
>>> TC
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: User access on a company intranet
    ... Access always uses a workgroup file, ... database, it silently logs you in as a user named 'Admin'. ... When you want to implement security, you create a new mdw file, and follow ... to open the secure mdb is by using the mdw you created. ...
    (microsoft.public.access.security)
  • Re: Do not have necessary permission to use?
    ... the .mdw was placed in the recycle bin. ... If your database is actually secured, then create a desktop shortcut to ... Microsoft Access MVP ... I am not exactly sure how my workgroup file got changed. ...
    (microsoft.public.access.security)
  • Re: Problems setting up access security
    ... me the database, the workgroup file, and the shortcut, and everything worked ... The Admin user still owns the database object. ... You secured it using the system.mdw, thinking that you were using your secure mdw. ...
    (microsoft.public.access.security)
  • Re: Access 2003 Workgroup File
    ... a database can be associated with more than one workgroup file. ... If your 2003 database was secured properly, i.e. with the intent that it is only useable with one secure mdw, then you should only be able to open it while using the correct mdw file. ... Both have modified timestamps. ...
    (microsoft.public.access.security)
  • Re: Sorting out security
    ... > MS Access security. ... > created a new workgroup, added a password for the Admin role, added ... > remote logins to a secured database. ... The location of the current workgroup file is recorded in the ...
    (microsoft.public.access.security)
Loading