Re: Basic security questions

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: Basic security questions
    ... PS Do you have to use the Jet provider? ... > Password protected databases are different from database protected by ULS ... ULS protected databases require the use of the .mdw workgroup file ... >>> When you start an mdb file using a shortcut of the standard form, ...
    (microsoft.public.access.security)
  • Re: Basic security questions
    ... I'd like to have the database look for its workgroup file ... > If you double-click an mdb file, the sequence of actions is as follows. ... MS Access opens the default workgroup file for that PC; ...
    (microsoft.public.access.security)
  • Re: Define workgroup on activate event?
    ... I don't need each database to have its own workgroup file, ... I'm currently using a windows shortcut ... > Also if the users click on the mdb file directly, ...
    (microsoft.public.access.security)
  • Re: Access to zipped Microsoft Access database
    ... I have no problems with connecting to ms access database, ... I want to connect with a mdb file which is zipped. ... different file extensions can make that task little harder. ... For example on any unix based system using the file command will tell you what type a file is regardless of file extension. ...
    (comp.lang.java.databases)
  • Re: Basic security questions
    ... Access selects a workgroup file before ... it even /opens/ your database. ... If you double-click an mdb file, the sequence of actions is as follows. ... MS Access opens the default workgroup file for that PC; ...
    (microsoft.public.access.security)